AI agents use cache_touch to create or update resources in Amazon EKS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon EKS MCP Server environment.
The tool performs a reversible write operation that updates cache key metadata. While not destructive (the key/data isn't deleted), it modifies system state. Misuse by an agent could cause premature cache eviction of critical data or keep sensitive data cached longer than intended, affecting downstream applications.
From the tool's definition Tool description states 'Update the expiration time for a key' — this modifies metadata associated with cached data, changing its TTL or expiration timestamp.
Documented attack patterns abuse exactly the kind of access cache_touch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon EKS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cache_touch:
{
"version": "1",
"default": "deny",
"tools": {
"cache_touch": {
"limits": [
{
"counter": "cache_touch_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}cache_touch 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.
Update the expiration time for a key. It is categorised as a Write tool in the Amazon EKS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon EKS MCP Server MCP server in PolicyLayer and add a rule for cache_touch: 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 EKS MCP Server. Nothing to install.
cache_touch 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_touch 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_touch. 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_touch is provided by the Amazon EKS MCP Server MCP server (awslabs.eks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon EKS 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 EKS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.