Replace a value in the cache only if the key exists.
AI agents use cache_replace to create or update resources in Amazon MQ MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon MQ MCP Server environment.
This tool modifies cached data in a reversible manner by replacing values. While it could affect application behavior depending on what is cached, it is not destructive (data can be overwritten again), not financial, and not code execution. The impact is isolated to cache layer with medium severity blast radius if misused to corrupt cache state.
From the tool's definition Tool description states 'Replace a value in the cache' which is a modification operation. The conditional 'only if the key exists' indicates it updates existing data reversibly.
Attacks that exploit this kind of access
Replace a value in the cache only if the key exists. It is categorised as a Write tool in the Amazon MQ MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for cache_replace: 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 Amazon MQ MCP Server. Nothing to install.
cache_replace 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_replace 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_replace. 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_replace is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.