cache_decr
Decrement a counter in the cache. Args: key: The key to decrement value: Amount to decrement by (default 1) Returns: New value or error message
This record as markdown: /tools/aws/cache-decr.md
What cache_decr does on AWS
AI agents use cache_decr to create or update resources in AWS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS environment.
Why cache_decr is rated Medium
This tool modifies an existing value in the cache by decrementing a counter. It is a write operation (mutates state) but is generally reversible (the counter can be incremented back). Misuse could corrupt application state or logic that depends on cache counters, hence medium severity.
From the tool's definition Decrement a counter in the cache
Attacks that exploit this kind of access
The rule that runs cache_decr 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_decr, this is the rule to start with:
cache_decr stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_decr call is checked against it from then on.
Questions about cache_decr
Decrement a counter in the cache. Args: key: The key to decrement value: Amount to decrement by (default 1) Returns: New value or error message. It is categorised as a Write tool in the AWS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS MCP server in PolicyLayer and add a rule for cache_decr: 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_decr is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the cache_decr 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_decr. 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_decr 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