This record as markdown: /tools/mcp-dev/delete-template.md
What delete-template does on Mcp Dev
AI agents call delete-template to permanently remove resources in Mcp Dev, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete-template is rated Critical
This tool permanently removes a template from an Umbraco CMS system. Template deletion cannot be undone and affects the structure of content presentation. While not catastrophic across all site content, it is a destructive operation that warrants high severity as templates are critical infrastructure components in CMS systems.
From the tool's definition Tool name is 'delete-template' and description states 'Deletes a template by Id'. The verb 'deletes' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete-template safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete-template, this is the rule to start with:
delete-template is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every delete-template call is checked against it from then on.
Questions about delete-template
Deletes a template by Id. It is categorised as a Destructive tool in the Mcp Dev MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for delete-template: 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 Mcp Dev. Nothing to install.
delete-template 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-template 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-template. 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-template is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Dev, and thousands of servers like it.
Across the catalogue