cache_quit

THE RISK

Low Risk

Why cache_quit needs a policy

This tool closes a connection to a cache server, which is a connection management operation. It doesn't read data, write/modify data, execute commands, destroy data, or involve financial transactions. Closing a connection is a cleanup/lifecycle operation that falls under 'Other'. Severity is low as it may interrupt caching but has limited 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:

POLICY

How to control cache_quit

PolicyLayer is an MCP gateway — it sits between your AI agents and Prometheus MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cache_quit:

policy.json

{
  "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.

Create a free account and register Prometheus MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Prometheus MCP Server tools

Destructive bulk_delete_by_criteria bulk_delete_by_criteria Destructive cache_delete Delete a value from the cache. Destructive cache_delete_many Delete multiple values from the cache. Destructive cache_delete_multi Delete multiple values from the cache (alias for delete_many). Destructive delete delete Destructive delete_access_key delete_access_key Destructive delete_agent_runtime delete_agent_runtime Destructive delete_agent_runtime_endpoint delete_agent_runtime_endpoint

All 805 Prometheus MCP Server tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cache_quit

What does the cache_quit tool do? +

Close the connection to the cache server. It is categorised as a Other tool in the Prometheus MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on cache_quit? +

Register the Prometheus 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 Prometheus MCP Server. Nothing to install.

What risk level is cache_quit? +

cache_quit is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cache_quit? +

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.

How do I block cache_quit completely? +

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.

What MCP server provides cache_quit? +

cache_quit is provided by the Prometheus MCP Server MCP server (awslabs.prometheus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Prometheus MCP Server tool call.

Start from Prometheus MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →