Check the health and status of the Memro MCP server and its connections.
AI agents call get_system_status to retrieve information from memro MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diagnostic information about system health and connectivity status. It performs no data modifications, does not execute code or external operations, and cannot cause destructive or financial impacts. It is a pure information retrieval (Read) operation with minimal risk of misuse.
From the tool's definition Tool name 'get_system_status' and description 'Check the health and status of the Memro MCP server and its connections' indicate a read-only operation that queries server state without modifying, executing external operations, or causing side effects.
Attacks that exploit this kind of access
Check the health and status of the Memro MCP server and its connections. It is categorised as a Read tool in the memro MCP Server MCP Server, which means it retrieves data without modifying state.
Register the memro MCP Server MCP server in PolicyLayer and add a rule for get_system_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 memro MCP Server. Nothing to install.
get_system_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 get_system_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 get_system_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.
get_system_status is provided by the memro MCP Server MCP server (memrohq/memro-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 →