AI agents call delete-endpoint to permanently remove resources in RunPod MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of endpoints cannot be undone and will disrupt services relying on those endpoints. This is categorized as Destructive rather than Write because the operation is irreversible. Severity is high because endpoint deletion affects live infrastructure and services, though not as critical as financial operations.
From the tool's definition Tool name 'delete-endpoint' indicates irreversible deletion. Server context shows it manages RunPod infrastructure including endpoints (API inference endpoints).
Documented attack patterns abuse exactly the kind of access delete-endpoint gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RunPod MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-endpoint:
{
"version": "1",
"default": "deny",
"hide": [
"delete-endpoint"
]
}delete-endpoint 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.
delete-endpoint. It is categorised as a Destructive tool in the RunPod MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RunPod MCP Server MCP server in PolicyLayer and add a rule for delete-endpoint: 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 RunPod MCP Server. Nothing to install.
delete-endpoint 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 delete-endpoint 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 delete-endpoint. 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.
delete-endpoint is provided by the RunPod MCP Server MCP server (runpod/runpod-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 RunPod MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 RunPod MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.