trade_history
AI agents call trade_history to retrieve information from Trading MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to retrieve historical trading records, which is a read-only operation with no side effects. While the description is empty (reducing confidence slightly), the naming convention and positioning among other query-focused portfolio tools (pnl, portfolio, unrealized_gains) strongly suggest this is a data retrieval function.
From the tool's definition Tool name 'trade_history' with sibling tools focused on querying portfolio data (current_price, pnl, portfolio, unrealized_gains). Despite empty description, the name and context indicate historical data retrieval rather than modification or execution.
Attacks that exploit this kind of access
trade_history. It is categorised as a Read tool in the Trading MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Trading MCP Server MCP server in PolicyLayer and add a rule for trade_history: 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 MCP Server. Nothing to install.
trade_history 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 trade_history 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 trade_history. 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.
trade_history is provided by the Trading MCP Server MCP server (vaishnavik23/trading-mcp-server). 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 →