Close the connection to the cache server.
AI agents call cache_quit as a supporting operation in Amazon MQ MCP Server workflows.
This tool closes a connection to a cache server, which is a session/resource management operation. It doesn't read, write, execute code, destroy data, or involve financial transactions. It simply terminates a network connection, which is reversible (a new connection can be opened). This falls into 'Other' as it is a housekeeping/lifecycle operation with minimal blast radius.
From the tool's definition Close the connection to the cache server
Attacks that exploit this kind of access
Close the connection to the cache server. It is categorised as a Other tool in the Amazon MQ MCP Server MCP Server, which means it performs auxiliary operations.
Register the Amazon MQ MCP Server 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 Amazon MQ MCP Server. 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 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.