Delete a routine by name. Always confirm with user that they want to delete it. User may supply a name that
AI agents call delete-routine to permanently remove resources in Routine — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes user-created routines that cannot be recovered. While the blast radius is scoped to the user's own routine definitions (not system-critical data), deletion is irreversible. The confirmation requirement mitigates some risk but does not change the destructive nature. This is more severe than Write (which is reversible) and belongs in Destructive category.
From the tool's definition Tool name is 'delete-routine' and description states 'Delete a routine by name', which irreversibly removes a stored routine. The description explicitly mentions deletion without undo capability.
Attacks that exploit this kind of access
Delete a routine by name. Always confirm with user that they want to delete it. User may supply a name that. It is categorised as a Destructive tool in the Routine MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Routine MCP server in PolicyLayer and add a rule for delete-routine: 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 Routine. Nothing to install.
delete-routine 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-routine 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-routine. 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-routine is provided by the Routine MCP server (mquan/mcp-routine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →