Get orders from history within the specified date range. Args: symbol: Symbol name group: Filter for arranging a group of orders ticket: Order ticket position: Position ticket from_date: Start date for order retrieval to_date: End date for order retrieval Returns: List[HistoryOrder]: List of hist...
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 read-only historical order data within a specified date range. It has no side effects and cannot modify account state, execute trades, or cause financial transactions. The parameters are all filters for querying existing data. While it accesses financial information (trading history), the action itself is purely informational retrieval, making it a Read category tool with low severity.
From the tool's definition Tool name 'history_orders_get' and description 'Get orders from history' indicate retrieval of historical trading data.
Documented attack patterns abuse exactly the kind of access history_orders_get gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MetaTrader 5 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for history_orders_get:
{
"version": "1",
"default": "deny",
"tools": {
"history_orders_get": {}
}
}history_orders_get is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get orders from history within the specified date range. Args: symbol: Symbol name group: Filter for arranging a group of orders ticket: Order ticket position: Position ticket from_date: Start date for order retrieval to_date: End date for order retrieval Returns: List[HistoryOrder]: List of historical orders. 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 (qoyyuum/mcp-metatrader5-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 26 MetaTrader 5 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
26 MetaTrader 5 MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.