This record as markdown: /tools/aws/cache-flush-all.md
What cache_flush_all does on AWS
AI agents call cache_flush_all to permanently remove resources in AWS, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cache_flush_all is rated Critical
Flushing all cache entries is an irreversible bulk operation — once evicted, cached data is gone and cannot be restored. This qualifies as Destructive with high severity because misuse by an AI agent would instantly wipe all cached data, potentially causing cascading failures, increased latency, or data loss depending on the cache's role in the system.
From the tool's definition Flush all cache entries
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs cache_flush_all 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_flush_all, this is the rule to start with:
cache_flush_all is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every cache_flush_all call is checked against it from then on.
Questions about cache_flush_all
Flush all cache entries. Args: delay: Optional delay in seconds before flushing Returns: Success message or error message. It is categorised as a Destructive tool in the AWS MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS MCP server in PolicyLayer and add a rule for cache_flush_all: 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_flush_all is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cache_flush_all 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_flush_all. 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_flush_all 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.
Across the catalogue