AI agents call account_get_max_size to retrieve information from Okx Trade without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
px | string | — | Limit order price (omit for market) |
ccy | string | — | Margin currency. Required for isolated mode. |
instId | string | Yes | e.g. BTC-USDT-SWAP |
tdMode | string | Yes | |
leverage | string | — | Leverage (defaults to account setting) |
Parameters from the server's own tool schema.
This tool retrieves calculated information about account capacity without side effects. It reads current balance and leverage to compute a maximum size value, used to inform trading decisions but does not execute trades, move funds, or modify account state. It is a pure read operation typical of pre-trade risk checks.
From the tool's definition Tool name 'account_get_max_size' and description states it is for querying/retrieving ('Get') the maximum order size—a read-only calculation based on current account state. No order placement, modification, or financial transaction occurs.
Attacks that exploit this kind of access
Get max buy/sell order size for a SWAP/FUTURES instrument given current balance and leverage. Useful before placing orders. It is categorised as a Read tool in the Okx Trade MCP Server, which means it retrieves data without modifying state.
account_get_max_size accepts 5 parameters: px, ccy, instId, tdMode, leverage. Required: instId, tdMode. The full parameter table on this page comes from the server's own tool schema.
Register the Okx Trade MCP server in PolicyLayer and add a rule for account_get_max_size: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Okx Trade. Nothing to install.
account_get_max_size is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the account_get_max_size rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for account_get_max_size. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
account_get_max_size is provided by the Okx Trade MCP server (@okx_ai/okx-trade-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →