Skip to content

Agent Skill · version 0.1.0

Set trading limits for an AI agent

Read and verify Fensory account controls, then guide the user through any app-side changes. The skill does not place, cancel or replace orders.

Download and review

Download the public file, review every instruction, then place it in the skills directory documented by the compatible client you use. Client-specific paths are omitted until each workflow is verified.

Download
curl -fsSL https://fensory.com/skills/set-agent-trade-limits/SKILL.md -o SKILL.md

What the skill instructs

  • Read the account and instrument before preparing an action.
  • Keep the proposal inside the user's ceiling and the account's per-order cap.
  • Show the exact symbol, side, order type and size before a write call. Include the limit price for a limit order, or the current quote and expected execution conditions for a market order, then ask for confirmation.
  • Report a prepared order, submitted order and fill as three different states.

SKILL.md

---
name: fensory-trade-limits
description: Read and verify Fensory account controls, then guide the user through any app-side changes. The skill does not place, cancel or replace orders.
license: Proprietary
compatibility: Requires access to the Fensory MCP server and an eligible Fensory account. Fensory is not available to US persons.
metadata:
  author: Fensory AG
  version: "0.1.0"
  source: "https://fensory.com/skills/set-agent-trade-limits"
---

# Set trading limits for an AI agent

## When to use

This guide is for anyone connecting Claude, ChatGPT, Hermes, OpenClaw, Codex or Cursor to a funded Fensory account and deciding what the assistant may trade before enabling agentic trading.

It is not an investment policy and it does not select markets for you. The controls contain execution permissions. They do not predict prices, guarantee a maximum total loss or replace checking positions and open orders.

## Operating rules

- Start with read tools and identify the signed-in account, market, venue and instrument before preparing an action.
- Treat the Fensory account state, open orders, positions and fills as authoritative when they differ from the conversation.
- Fensory enforces three controls on the account: a kill-switch, a market allow-list and a per-order cap. Client confirmation instructions are separate from those account controls.
- Never describe a perpetual future as a share or tokenized equity. State the instrument and its risks before discussing an order.
- Never substitute a different market, quote currency or instrument because the requested one is unavailable.
- Keep every proposed order within both the user's stated ceiling and the account's per-order cap.
- Do not place, cancel or replace an order until the exact symbol, side, order type and size have been shown. For a limit order, show the limit price. For a market order, show the current quote and expected execution conditions. The user must confirm that exact action.
- Stop when a required tool is unavailable, the account limit cannot be verified, the quote is stale or the instrument is ambiguous.

## Risk and scope

This file is operational guidance, not financial advice. Trading can lose the full amount committed. Perpetual futures use margin and can be liquidated. Spot assets can lose value. Stop if the instrument, current quote or account controls cannot be verified.

## Procedure

1. **Keep agentic trading disabled while you configure.** Fund and inspect the account first. With agentic trading disabled, an assistant can use read tools while trading tools fail.
2. **Choose the exact markets.** Use the market tools to distinguish spot, tokenized assets and perpetual futures. Add only the intended instrument to the account allow-list; enabling a ticker name without checking the instrument is not enough. Tools: `get_all_markets`, `get_market`, `get_spot_metadata`.
3. **Set the maximum size of one order.** The cap is checked before an order reaches a venue. Set it in the app, then ask the connected assistant to read the account so the displayed ceiling and the account response agree. Tools: `get_account_state`, `get_spot_account_state`.
4. **Test with read-only scenarios.** Ask the assistant to evaluate orders below, at and above the ceiling without submitting them. The test confirms its understanding and leaves the account unchanged. Tools: `get_open_orders`, `get_perps_status`.
5. **Enable trading only when the report is correct.** Turn agentic trading on in the app after the market list, cap, positions and open orders are understood. Disable agentic trading in the app to stop new trading actions when the test ends.

## Request template

Read my Fensory account controls and report them without changing anything. Show whether agentic trading is enabled, the per-order cap, every allowed market, current positions and all open orders. Separate spot from perpetual futures and identify any shared ticker that refers to different instruments.

Then test these three hypothetical orders against the controls: one order $1 below the cap, one exactly at the cap and one $1 above it. Do not submit, cancel or replace anything. Explain which request the account would accept or reject, what the per-order cap does not limit, and how I would stop all new trading actions by disabling agentic trading in the app.

## Failure handling

- **The cap is mistaken for a total-loss limit:** A $100 per-order cap rejects a $101 order. It can still allow several $100 orders, and positions can lose value after they fill. Monitor cumulative exposure separately.
- **A ticker maps to the wrong instrument:** Tesla can appear as a tokenized equity in the app and a perpetual future on the MCP path. The allow-list must identify the instrument, because custody and liquidation risk differ.
- **An old order remains open:** Disabling agentic trading stops new trading actions and does not erase a fill or resting order. Read open orders and positions before assuming the account has no remaining exposure.
- **The assistant account is compromised:** The same allow-list and cap still apply. Whoever controls the assistant could place allowed orders under the cap, and those orders can lose money. Disable agentic trading in the app immediately.
- **Client permissions and account limits are confused:** A client can hide or confirm a tool, while Fensory enforces the account controls. Keep both layers restrictive. A permissive client cannot raise the Fensory account cap.

## Response contract

Report the account used, the exact instrument, the tools called, the controls that applied and the current order or position state. Separate a prepared order from a submitted order, and a submitted order from a fill. If no action was taken, say so directly.

## Sources

- [Fensory security model](https://fensory.com/security)
- [Fensory MCP server](https://fensory.com/mcp)
- [Fensory FAQ](https://fensory.com/faq)

Product behavior and client permissions verified 2026-10-08.

Questions people ask

Can an AI agent change its own Fensory limits?
No. The controls are account settings changed in the Fensory app: a kill-switch, a market allow-list and a per-order cap. A prompt cannot raise the ceiling.
What does the per-order cap stop?
It stops any single order above the value you set. A $100 cap means no one order is $101. It does not cap the number of orders, total exposure or total loss.
What does the market allow-list stop?
It makes markets outside the approved list unreachable to trading tools. Spot and perpetual futures are authorized separately, so enabling one does not enable the other.
What happens when I disable agentic trading?
New trading actions fail at the account layer. Existing fills, positions and resting orders remain in the account, so inspect them after switching trading off.
Can the agent withdraw funds if it is compromised?
No. On the current MCP path, the Hyperliquid signing key cannot withdraw, transfer or bridge funds. A compromised assistant can still place allowed orders under the cap until agentic trading is disabled.