get_open_positions
AI agents call get_open_positions 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 tool retrieves MetaTrader 5 account position data without modifying, deleting, or executing any trades. The server explicitly provides 'read-only access' and this tool performs a query/fetch operation typical of the Read category. Even though the description field is empty, the name and server context strongly indicate a retrieval operation with no side effects.
From the tool's definition Tool name 'get_open_positions' combined with server description stating 'read-only access to positions' and sibling tools like 'get_all_open_positions', 'get_account_info', 'get_trade_history' all indicating data retrieval operations.
Attacks that exploit this kind of access
get_open_positions. 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_open_positions: 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_open_positions 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_open_positions 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_open_positions. 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_open_positions 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 →