Critical Risk →

stream_group_destroy

Destroy consumer group.

How to control stream_group_destroy ↓

What stream_group_destroy does on Prometheus MCP Server

AI agents call stream_group_destroy to permanently remove resources in Prometheus MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why stream_group_destroy needs a policy

The verb 'destroy' combined with 'consumer group' indicates an irreversible deletion operation that cannot be undone. This falls squarely into the Destructive category rather than Execute, as it performs a specific destructive action on infrastructure rather than executing arbitrary operations.

From the tool's definition Tool name 'stream_group_destroy' with description 'Destroy consumer group.' indicates irreversible deletion of a Kafka/stream consumer group resource.

Documented attack patterns abuse exactly the kind of access stream_group_destroy gives an agent:

How to control stream_group_destroy

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 stream_group_destroy:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "stream_group_destroy"
  ]
}

stream_group_destroy disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about stream_group_destroy

What does the stream_group_destroy tool do? +

Destroy consumer group. It is categorised as a Destructive tool in the Prometheus MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on stream_group_destroy? +

Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for stream_group_destroy: 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 stream_group_destroy? +

stream_group_destroy is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit stream_group_destroy? +

Yes. Add a rate_limit block to the stream_group_destroy 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 stream_group_destroy completely? +

Set action: deny in the PolicyLayer policy for stream_group_destroy. 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 stream_group_destroy? +

stream_group_destroy 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.

Free to start. No card required.

805 Prometheus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.