Return aggregated stats from all logged trades.
AI agents call get_trading_stats to retrieve information from Trading Analysis 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 read operation that queries and aggregates already-logged trade information. There are no side effects, no data modification, no code execution, and no financial transactions triggered. The tool simply retrieves and presents analytical summaries. While trading data may be sensitive, the tool itself performs no destructive or risky operations.
From the tool's definition The tool returns aggregated statistics from existing trade data with no modification capability. The description uses 'Return' which indicates data retrieval only.
Attacks that exploit this kind of access
Return aggregated stats from all logged trades. It is categorised as a Read tool in the Trading Analysis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Trading Analysis MCP Server MCP server in PolicyLayer and add a rule for get_trading_stats: 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 Trading Analysis MCP Server. Nothing to install.
get_trading_stats 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_stats 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_stats. 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_stats is provided by the Trading Analysis MCP Server MCP server (zkyko/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 →