get_memory_stats
AI agents call get_memory_stats to retrieve information from Cluster Execution MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve memory statistics from the cluster system. While the description is empty (lowering confidence slightly), the 'get_' prefix and context of a cluster monitoring server strongly suggest a read-only query operation that gathers diagnostic information without modifying any state or executing commands.
From the tool's definition Tool name 'get_memory_stats' and server description indicate this queries memory statistics from cluster nodes. No description provided, but 'get' is a standard retrieval verb with no side effects.
Attacks that exploit this kind of access
get_memory_stats. It is categorised as a Read tool in the Cluster Execution MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cluster Execution MCP Server MCP server in PolicyLayer and add a rule for get_memory_stats: 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 Cluster Execution MCP Server. Nothing to install.
get_memory_stats 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_memory_stats 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_memory_stats. 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_memory_stats is provided by the Cluster Execution MCP Server MCP server (marc-shade/cluster-execution-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 →