Get information about the MetaTrader 5 terminal.
AI agents call get_terminal_info 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 is a pure read operation that queries terminal metadata (version, connection status, settings, etc.). It has no side effects, cannot modify data, execute trades, or cause financial impact. The blast radius of misuse is minimal—an agent could only gain informational access to terminal configuration.
From the tool's definition Tool name 'get_terminal_info' and description 'Get information about the MetaTrader 5 terminal' indicate a retrieval operation with no modification or execution capabilities. Returns informational data about terminal state/configuration.
Attacks that exploit this kind of access
Get information about the MetaTrader 5 terminal. 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 get_terminal_info: 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.
get_terminal_info 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_terminal_info 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_terminal_info. 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_terminal_info is provided by the MetaTrader 5 MCP Server MCP server (sameerasulakshana/mcpmt5). 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 →