Replace a value in the cache only if the key exists.
AI agents use cache_replace to create or update resources in Amazon Translate MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon Translate MCP Server environment.
This is a reversible modification of cached data. It reads and overwrites an existing cache value conditionally, which qualifies as Write. The impact is low because cache operations are typically temporary and non-persistent; corrupting a cache value would at worst require a restart or refresh, with no permanent data loss or side effects beyond the cache scope.
From the tool's definition The tool description indicates it 'Replace[s] a value in the cache' — an operation that modifies data. The conditional 'only if the key exists' confirms this is an update operation, not a deletion or creation of new entries.
Documented attack patterns abuse exactly the kind of access cache_replace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Translate MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cache_replace:
{
"version": "1",
"default": "deny",
"tools": {
"cache_replace": {
"limits": [
{
"counter": "cache_replace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}cache_replace 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.
Free to start. No card required.
Replace a value in the cache only if the key exists. It is categorised as a Write tool in the Amazon Translate MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon Translate 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 Translate 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 Translate MCP Server MCP server (awslabs.amazon-translate-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon Translate MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Amazon Translate MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.