check_vps_status
AI agents call check_vps_status 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 checks the status of a VPS connection, which is a read-only monitoring operation that retrieves state information without modifying, executing, or deleting any data. The empty description is supplemented by the server's stated read-only purpose and the pattern of sibling tools, all of which are information retrieval operations. The blast radius is minimal—status checks cannot affect trading or account data.
From the tool's definition Tool name 'check_vps_status' and server description indicating 'read-only access' to monitoring capabilities. Sibling tools include query functions like get_account_info, get_open_positions, get_trade_history, which are all Read operations.
Attacks that exploit this kind of access
check_vps_status. 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 check_vps_status: 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.
check_vps_status 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 check_vps_status 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 check_vps_status. 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.
check_vps_status 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 →