delete_template

Delete a template by ID.

SERVER1c Templates SOURCEdesko77/1c-templates-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/desko77-1c-templates-mcp/delete-template.md

WHAT IT DOES

What delete_template does on 1c Templates

AI agents call delete_template to permanently remove resources in 1c Templates, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_template is rated Critical

This tool removes templates from the database with no undo mechanism. Deletion is irreversible and constitutes a destructive operation. While the blast radius is limited to template data rather than critical systems, unauthorized or mistaken deletion of community templates (from a collection of 2262+) could harm users relying on those templates.

From the tool's definition delete_template: Delete a template by ID. The tool name and description explicitly indicate irreversible deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_template safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 1c Templates, 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 Hidden

delete_template is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_template"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 1c Templates, apply this rule, and every delete_template call is checked against it from then on.

FAQ

Questions about delete_template

What does the delete_template tool do? +

Delete a template by ID. It is categorised as a Destructive tool in the 1c Templates 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 delete_template? +

Register the 1c Templates 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 1c Templates. Nothing to install.

What risk level is delete_template? +

delete_template 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 delete_template? +

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.

How do I block delete_template completely? +

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.

What MCP server provides delete_template? +

delete_template is provided by the 1c Templates MCP server (desko77/1c-templates-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 1c Templates, and thousands of servers like it.

This server

All 6 1c Templates tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →