AI agents call get_history to retrieve information from MCP MetaTrader 4 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 data from the MetaTrader 4 account. It performs a query operation that returns past transaction information without creating, modifying, deleting, or executing any trades. The blast radius of misuse is minimal—an attacker could only view sensitive account history but cannot execute trades, modify positions, or cause financial harm through this tool alone.
From the tool's definition Tool name 'get_history' and description 'Get trading history' indicate data retrieval with no modification or side effects. The verb 'get' and context of reading historical trading records align with Read category operations.
Documented attack patterns abuse exactly the kind of access get_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP MetaTrader 4 Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_history": {}
}
}get_history 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 trading history. It is categorised as a Read tool in the MCP MetaTrader 4 Server MCP Server, which means it retrieves data without modifying state.
Register the MCP MetaTrader 4 Server MCP server in PolicyLayer and add a rule for get_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 MCP MetaTrader 4 Server. Nothing to install.
get_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 get_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 get_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.
get_history is provided by the MCP MetaTrader 4 Server MCP server (8nite/metatrader-4-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP MetaTrader 4 Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 MCP MetaTrader 4 Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.