AI agents call delete_service to permanently remove resources in Render — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a service, which cannot be undone. Deletion of cloud-deployed services is a destructive operation with significant blast radius—an AI agent misusing this could remove production services, causing service outages and data loss. This is more severe than Write (which is reversible) or Execute (which may have side effects but not necessarily permanent ones).
From the tool's definition Tool name is 'delete_service' with description 'Delete a service'. The action irreversibly removes a deployed service from the Render platform.
Documented attack patterns abuse exactly the kind of access delete_service gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Render, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_service:
{
"version": "1",
"default": "deny",
"hide": [
"delete_service"
]
}delete_service 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 a service. It is categorised as a Destructive tool in the Render MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Render MCP server in PolicyLayer and add a rule for delete_service: 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 Render. Nothing to install.
delete_service 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_service 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_service. 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_service is provided by the Render MCP server (niyogi/render-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Render, 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.
8 Render tools catalogued and risk-classified — across an index of 43,000+ MCP servers.