Get detailed cache performance statistics and health metrics
AI agents call cache_stats to retrieve information from r3 (Recall) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves performance metrics and health statistics from the cache system. It performs no side effects, does not modify data, does not execute external operations, and does not delete or move resources. It is a simple diagnostic read operation that returns informational data about system state.
From the tool's definition Tool name 'cache_stats' and description 'Get detailed cache performance statistics and health metrics' indicate purely observational/diagnostic functionality that retrieves statistics without modifying or executing operations.
Attacks that exploit this kind of access
Get detailed cache performance statistics and health metrics. It is categorised as a Read tool in the r3 (Recall) MCP Server, which means it retrieves data without modifying state.
Register the r3 (Recall) MCP server in PolicyLayer and add a rule for 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 r3 (Recall). Nothing to install.
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 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 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.
cache_stats is provided by the r3 (Recall) MCP server (n3wth/r3). 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 →