Critical Risk →

gateway_delete

gateway_delete

How to control gateway_delete ↓

What gateway_delete does on Prometheus MCP Server

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

Although the description is empty (lowering confidence slightly), the tool name unambiguously indicates a destructive action. In the context of an AWS Prometheus server, 'gateway_delete' most likely deletes an API Gateway, network gateway, or similar infrastructure resource. Deletion operations are irreversible and represent the highest severity risk category.

From the tool's definition Tool name 'gateway_delete' combined with Prometheus MCP Server context indicates a deletion operation on AWS infrastructure components. The 'delete' verb is explicit and irreversible.

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

How to control gateway_delete

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

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

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

What does the gateway_delete tool do? +

gateway_delete. 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 gateway_delete? +

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

What risk level is gateway_delete? +

gateway_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 gateway_delete? +

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

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

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