Get account configuration: position mode (net vs hedge), account level, auto-loan settings, etc. Note: settleCcy is the current settlement currency for USDS-margined contracts. settleCcyList is the list of available settlement currencies to choose from. These fields only apply to USDS-margined co...
AI agents call account_get_config 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.
This tool retrieves account settings and preferences without modifying any data or triggering financial transactions. It is a read-only query of configuration state. While it accesses account information, the blast radius of misuse is limited to information disclosure rather than financial loss or account modification. Classified as Read with low severity.
From the tool's definition Tool name 'account_get_config' and description 'Get account configuration' indicate a retrieval operation with no mutation of data. Returns configuration settings like position mode, account level, and settlement currency preferences.
Attacks that exploit this kind of access
Get account configuration: position mode (net vs hedge), account level, auto-loan settings, etc. Note: settleCcy is the current settlement currency for USDS-margined contracts. settleCcyList is the list of available settlement currencies to choose from. These fields only apply to USDS-margined contracts and can be ignored for standard USDT/coin-margined trading. It is categorised as a Read tool in the Okx Trade MCP Server, which means it retrieves data without modifying state.
Register the Okx Trade MCP server in PolicyLayer and add a rule for account_get_config: 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_config 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_config 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_config. 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_config 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 →