View your complete trade history — every order fill with prices, fees, and realized P&L.
AI agents call trading_history to retrieve information from Purple Flea Trading without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves past transaction records and financial performance metrics without creating, modifying, or deleting data. While classified as Read (no side effects), severity is elevated to medium because the returned data is financially sensitive (prices, fees, P&L) and could expose patterns useful for market manipulation or account compromise if exposed to an attacker, though the tool itself poses no direct…
From the tool's definition Tool name 'trading_history' and description 'View your complete trade history — every order fill with prices, fees, and realized P&L' indicate retrieval and querying of historical trading data with no modification capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
View your complete trade history — every order fill with prices, fees, and realized P&L. It is categorised as a Read tool in the Purple Flea Trading MCP Server, which means it retrieves data without modifying state.
Register the Purple Flea Trading MCP server in PolicyLayer and add a rule for trading_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 Purple Flea Trading. Nothing to install.
trading_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 trading_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 trading_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.
trading_history is provided by the Purple Flea Trading MCP server (purple-flea/agent-trading). 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 →