Critical Risk →

DeleteDbInstance

Deletes a Timestream for InfluxDB DB instance by the instance-identifier

How to control DeleteDbInstance ↓

What DeleteDbInstance does on Prometheus MCP Server

AI agents call DeleteDbInstance 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 DeleteDbInstance needs a policy

Deletion of a database instance is an irreversible action that cannot be undone without restore operations (if available). This has severe blast radius: an AI agent invoking this with incorrect or malicious arguments could permanently destroy a production database and its data.

From the tool's definition Tool name 'DeleteDbInstance' and description 'Deletes a Timestream for InfluxDB DB instance' directly indicate irreversible deletion of a database instance.

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

How to control DeleteDbInstance

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

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

DeleteDbInstance 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 DeleteDbInstance

What does the DeleteDbInstance tool do? +

Deletes a Timestream for InfluxDB DB instance by the instance-identifier. 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 DeleteDbInstance? +

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

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

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

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

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