cache_stats
Get cache statistics. Args: args: Optional list of stats to retrieve Returns: Statistics or error message
This record as markdown: /tools/aws/cache-stats.md
What cache_stats does on AWS
AI agents call cache_stats to retrieve information from AWS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why cache_stats is rated Low
This tool retrieves statistics from a cache system. The verb 'Get' and the read-only nature of statistics gathering place it squarely in the Read category. There are no side effects, no data modification, no code execution, and no destructive operations.
From the tool's definition Tool name 'cache_stats' and description 'Get cache statistics' indicate a query operation that retrieves monitoring/diagnostic data without modifying state.
Attacks that exploit this kind of access
The rule that runs cache_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cache_stats, this is the rule to start with:
cache_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every cache_stats call is checked against it from then on.
Questions about cache_stats
Get cache statistics. Args: args: Optional list of stats to retrieve Returns: Statistics or error message. It is categorised as a Read tool in the AWS MCP Server, which means it retrieves data without modifying state.
Register the AWS 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 AWS. 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 AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AWS, and thousands of servers like it.
This server
Across the catalogue