Critical Risk →

collections_delete

Delete a collection.

Part of the Prometheus MCP server.

collections_delete can permanently delete data in Prometheus MCP, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE PROMETHEUS MCP →

Free to start. No card required.

AI agents may call collections_delete to permanently remove or destroy resources in Prometheus MCP. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call collections_delete in a loop, permanently destroying resources in Prometheus MCP. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

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

See the full Prometheus MCP policy for all 12 tools.

Get this rule live on your own Prometheus MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY PROMETHEUS MCP →

View all 12 tools →

These attack patterns abuse exactly the kind of access collections_delete gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so collections_delete only ever does what you allow.

SECURE PROMETHEUS MCP →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the collections_delete tool do? +

Delete a collection.. It is categorised as a Destructive tool in the Prometheus MCP 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 collections_delete? +

Register the Prometheus MCP server in PolicyLayer and add a rule for collections_delete: 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. Nothing to install.

What risk level is collections_delete? +

collections_delete 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 collections_delete? +

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

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

collections_delete is provided by the Prometheus MCP server (https://mcp.prometheus.sv/). 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 tool call.

Deterministic rules across all 12 Prometheus MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.