Deletes a Timestream for InfluxDB cluster by the db_cluster_id
AI agents call DeleteDbCluster 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.
This tool permanently removes a database cluster and all its associated data. Deletion is irreversible and cannot be undone. The blast radius is critical—an AI agent misusing this tool could destroy production databases, time-series data, and dependent services. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.'
From the tool's definition Tool name 'DeleteDbCluster' and description 'Deletes a Timestream for InfluxDB cluster' explicitly indicate irreversible deletion of a database cluster resource.
Documented attack patterns abuse exactly the kind of access DeleteDbCluster gives an agent:
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 DeleteDbCluster:
{
"version": "1",
"default": "deny",
"hide": [
"DeleteDbCluster"
]
} DeleteDbCluster disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Deletes a Timestream for InfluxDB cluster by the db_cluster_id. 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.
Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for DeleteDbCluster: 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.
DeleteDbCluster is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the DeleteDbCluster 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 DeleteDbCluster. 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.
DeleteDbCluster 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.
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.