AI agents call swap_get_leverage 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 |
|---|---|---|---|
instId | string | Yes | e.g. BTC-USDT-SWAP |
mgnMode | string | Yes |
Parameters from the server's own tool schema.
This tool retrieves leverage information for trading instruments. It does not create, modify, delete, or execute transactions. Even though it relates to a financial exchange (OKX), the action itself is informational—querying the current state of a leverage setting. No money moves, no positions change, and no irreversible actions occur. This is a classic Read operation with minimal blast radius if misused.
From the tool's definition Tool name 'swap_get_leverage' and description 'Get current leverage for a SWAP/FUTURES instrument' indicate a retrieval operation. The verb 'Get' and context of querying leverage settings show this is a read-only query with no side effects.
Attacks that exploit this kind of access
Get current leverage for a SWAP/FUTURES instrument. It is categorised as a Read tool in the Okx Trade MCP Server, which means it retrieves data without modifying state.
swap_get_leverage accepts 2 parameters: instId, mgnMode. Required: instId, mgnMode. 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 swap_get_leverage: 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.
swap_get_leverage 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 swap_get_leverage 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 swap_get_leverage. 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.
swap_get_leverage 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 →