Decrement a counter in the cache.
AI agents use cache_decr to create or update resources in AWS DynamoDB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS DynamoDB MCP Server environment.
Decrementing a counter modifies existing data (a counter value) in a reversible way — the counter can be incremented back. This is a Write operation. It does not delete data irreversibly, execute arbitrary code, or involve financial transactions. Severity is medium because misuse could corrupt application state or rate-limiting logic that depends on cache counters.
From the tool's definition Decrement a counter in the cache
Attacks that exploit this kind of access
Decrement a counter in the cache. It is categorised as a Write tool in the AWS DynamoDB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS DynamoDB MCP Server 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 DynamoDB MCP Server. 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 DynamoDB MCP Server MCP server (awslabs.dynamodb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.