Get cache statistics
AI agents call get_cache_stats to retrieve information from Memory Cache Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries cache statistics without side effects. It is a read-only operation that returns information about the cache state, fitting the 'Read' category. The severity is low because even if misused by an AI agent, it only exposes statistical metadata with no direct impact on data integrity, system operations, or external resources.
From the tool's definition Tool name 'get_cache_stats' and description 'Get cache statistics' indicate retrieval of statistical metadata about cached data. No modification, deletion, code execution, or financial operations are performed.
Attacks that exploit this kind of access
Get cache statistics. It is categorised as a Read tool in the Memory Cache Server MCP Server, which means it retrieves data without modifying state.
Register the Memory Cache Server MCP server in PolicyLayer and add a rule for get_cache_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 Memory Cache Server. Nothing to install.
get_cache_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_cache_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_cache_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_cache_stats is provided by the Memory Cache Server MCP server (tosin2013/mcp-memory-cache-server). 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 →