delete_template
Permanently delete an Elementor template from the library.
This record as markdown: /tools/vamerli-elementify-mcp/delete-template.md
What delete_template does on Elementify MCP
AI agents call delete_template to permanently remove resources in Elementify MCP, 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
An AI agent that decides to call delete_template doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Elementify MCP is gone. There is no undo for destructive operations.
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 Elementify MCP, 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 Elementify MCP, apply this rule, and every delete_template call is checked against it from then on.
Questions about delete_template
Permanently delete an Elementor template from the library. It is categorised as a Destructive tool in the Elementify MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Elementify 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 Elementify MCP. 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 Elementify MCP server (vamerli/elementify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Elementify, and thousands of servers like it.
Across the catalogue