Permanently delete a template. This cannot be undone.
AI agents call dual_delete_template to permanently remove resources in DUAL MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly deletes data (a template) with no recovery mechanism. Permanent deletion with explicit statement of being 'undoable' is the hallmark of the Destructive category. In a Web3/blockchain context, templates likely represent valuable schema or deployment configurations. An AI agent misusing this could destroy critical templates needed for token minting or infrastructure operations.
From the tool's definition Tool description explicitly states 'Permanently delete a template. This cannot be undone.'
Attacks that exploit this kind of access
Permanently delete a template. This cannot be undone. It is categorised as a Destructive tool in the DUAL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DUAL MCP Server MCP server in PolicyLayer and add a rule for dual_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 DUAL MCP Server. Nothing to install.
dual_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 dual_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 dual_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.
dual_delete_template is provided by the DUAL MCP Server MCP server (ro-ro-b/dual-mcp-server). 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 →