AI agents call list_local_eas 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 performs a simple enumeration or listing operation on local files/folders. It retrieves data (names and metadata of Expert Advisors) with no side effects, no code execution, no data modification, and no destructive impact. This is a classic Read operation—similar in character to 'list_experts' on the same server.
From the tool's definition Tool name 'list_local_eas' and description 'List EAs in the local development folders' indicate a read-only operation that retrieves information about Expert Advisors without modifying or executing them.
Documented attack patterns abuse exactly the kind of access list_local_eas 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 list_local_eas:
{
"version": "1",
"default": "deny",
"tools": {
"list_local_eas": {}
}
}list_local_eas 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.
List EAs in the local development folders. 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 list_local_eas: 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.
list_local_eas 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 list_local_eas 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 list_local_eas. 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.
list_local_eas 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.