history_orders_get
AI agents call history_orders_get to retrieve information from MetaTrader 5 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 trading orders from MetaTrader 5, which is a read-only operation with no side effects. It does not create, modify, delete, or execute trades. The absence of a description lowers confidence slightly, but the clear 'get' pattern on historical data strongly suggests a retrieval operation.
From the tool's definition Tool name 'history_orders_get' indicates retrieval of historical order data. The 'get' verb and 'history' context suggest read-only access to past trading records without modification or deletion.
Attacks that exploit this kind of access
history_orders_get. It is categorised as a Read tool in the MetaTrader 5 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MetaTrader 5 MCP Server MCP server in PolicyLayer and add a rule for history_orders_get: 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 MetaTrader 5 MCP Server. Nothing to install.
history_orders_get 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 history_orders_get 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 history_orders_get. 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.
history_orders_get is provided by the MetaTrader 5 MCP Server MCP server (jorgearturoyap-debug/metatrader-5-for-chatgpt-desktop). 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 →