AI agents call cache_quit as a supporting operation in Awslabs Valkey workflows.
This tool closes a network connection to the cache server. It does not read, write, execute, delete data, or involve financial operations. It is a connection lifecycle management operation — closing an existing session — which fits 'Other' best. Misuse could cause minor disruption (dropped connection) but has low blast radius.
From the tool's definition Close the connection to the cache server.
Documented attack patterns abuse exactly the kind of access cache_quit gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Awslabs Valkey, and nothing reaches the server without passing your rules. This is the rule we recommend for cache_quit:
{
"version": "1",
"default": "deny",
"tools": {
"cache_quit": {
"limits": [
{
"counter": "cache_quit_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}cache_quit gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Close the connection to the cache server. It is categorised as a Other tool in the Awslabs Valkey MCP Server, which means it performs auxiliary operations.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for cache_quit: 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 Awslabs Valkey. Nothing to install.
cache_quit is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cache_quit 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_quit. 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_quit is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Awslabs Valkey, 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 Awslabs Valkey tools catalogued and risk-classified — across an index of 43,000+ MCP servers.