get_account_info
AI agents call get_account_info 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.
This is a straightforward read operation that queries account data. The server explicitly constrains all tools to read-only access with no trade execution capability. Even if an AI agent misuses this tool, the blast radius is minimal—it merely retrieves information already owned by the account holder. No data is modified, deleted, or used to move money.
From the tool's definition Tool is part of 'mt5-remote-reader-mcp' server explicitly described as 'read-only access to positions, history, and logs without executing trades.' Tool name 'get_account_info' retrieves account information; sibling tools consistently follow get_* pattern for…
Attacks that exploit this kind of access
get_account_info. 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 get_account_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 Mt5 Remote Reader. Nothing to install.
get_account_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_account_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_account_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_account_info 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 →