Get trading configuration including max leverage, fees, and minimum position size.
AI agents call get_trading_config to retrieve information from TradeX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval tool that queries trading parameters. It has no capability to modify data, execute trades, delete records, or commit financial transactions. The information retrieved is informational only and supports decision-making rather than direct action. Low severity reflects minimal blast radius—misuse would only expose configuration details, not cause financial loss or irreversible changes.
From the tool's definition Tool name 'get_trading_config' and description 'Get trading configuration' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get trading configuration including max leverage, fees, and minimum position size. It is categorised as a Read tool in the TradeX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TradeX MCP Server MCP server in PolicyLayer and add a rule for get_trading_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 TradeX MCP Server. Nothing to install.
get_trading_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 get_trading_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 get_trading_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.
get_trading_config is provided by the TradeX MCP Server MCP server (tradexcards/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 →