list_local_eas

List EAs in the local development folders

SERVERMCP MetaTrader 4 Server SOURCE8nite/metatrader-4-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/8nite-metatrader-4-mcp/list-local-eas.md

WHAT IT DOES

What list_local_eas does on MCP MetaTrader 4 Server

AI agents call list_local_eas to retrieve information from MCP MetaTrader 4 Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_local_eas is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_local_eas safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP MetaTrader 4 Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_local_eas, this is the rule to start with:

list_local_eas Allowed

list_local_eas is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_local_eas": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP MetaTrader 4 Server, apply this rule, and every list_local_eas call is checked against it from then on.

FAQ

Questions about list_local_eas

What does the list_local_eas tool do? +

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.

How do I enforce a policy on list_local_eas? +

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.

What risk level is list_local_eas? +

list_local_eas is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_local_eas? +

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.

How do I block list_local_eas completely? +

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.

What MCP server provides list_local_eas? +

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.

KEEP EXPLORING

More on MCP MetaTrader 4 Server, and thousands of servers like it.

This server

All 14 MCP MetaTrader 4 Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →