list_terminals
AI agents call list_terminals to retrieve information from Mt5 Remote Reader without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or enumerate terminal instances available on the remote VPS. Combined with the server's explicit read-only mandate and the naming pattern of sibling tools focused on querying account/market data, this is a data retrieval operation with no side effects. The empty description slightly reduces confidence, but the context is clear enough to classify with reasonable certainty.
From the tool's definition Server is described as 'read-only access' to MetaTrader 5 data. Tool name 'list_terminals' follows the pattern of sibling tools (get_account_info, get_open_positions, get_symbol_info) that are retrieval operations.
Attacks that exploit this kind of access
list_terminals. It is categorised as a Read tool in the Mt5 Remote Reader MCP Server, which means it retrieves data without modifying state.
Register the Mt5 Remote Reader MCP server in PolicyLayer and add a rule for list_terminals: 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 Mt5 Remote Reader. Nothing to install.
list_terminals 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_terminals 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_terminals. 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_terminals is provided by the Mt5 Remote Reader MCP server (marco7734/mt5-remote-reader-mcp). 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 →