AI agents call account_get_max_avail_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 |
|---|---|---|---|
ccy | string | — | Margin currency. Required for isolated MARGIN mode. |
instId | string | Yes | e.g. BTC-USDT-SWAP or BTC-USDT |
tdMode | string | Yes | cash=spot |
reduceOnly | boolean | — | true=calculate max size for closing position |
Parameters from the server's own tool schema.
This tool queries account data to retrieve the maximum available size for position management. It is a read-only operation that returns informational data to support decision-making. While it relates to trading on a financial exchange, it does not itself move money, execute trades, or commit financial obligations. The 'get' pattern and 'retrieve' semantics confirm this is a Read category tool.
From the tool's definition Tool name contains 'get' and description states 'Get maximum available size' - retrieves position sizing information without modifying state or executing trades.
Attacks that exploit this kind of access
Get maximum available size for opening or reducing a position. Different from account_get_max_size which calculates new order size. It is categorised as a Read tool in the Okx Trade MCP Server, which means it retrieves data without modifying state.
account_get_max_avail_size accepts 4 parameters: ccy, instId, tdMode, reduceOnly. 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_avail_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_avail_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_avail_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_avail_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_avail_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 →