Fetch historical order data with pagination
AI agents call fetch_historical_order_data to retrieve information from Trading 212 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical order information with pagination support. It performs no side effects—no creation, modification, deletion, or execution of trades. The data returned is informational and read-only. Even in a financial trading context, merely accessing historical transaction records poses minimal risk compared to tools that execute trades or move funds.
From the tool's definition Tool name 'fetch_historical_order_data' and description 'Fetch historical order data with pagination' indicate data retrieval without modification. The verb 'fetch' combined with 'historical' denotes a query operation that accesses existing records.
Attacks that exploit this kind of access
Fetch historical order data with pagination. It is categorised as a Read tool in the Trading 212 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Trading 212 MCP Server MCP server in PolicyLayer and add a rule for fetch_historical_order_data: 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 212 MCP Server. Nothing to install.
fetch_historical_order_data 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 fetch_historical_order_data 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 fetch_historical_order_data. 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.
fetch_historical_order_data is provided by the Trading 212 MCP Server MCP server (razeevascx/212mcp). 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 →