Delete a token design by ID.
AI agents call dual_creative_design_delete 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.
This tool permanently removes a token design from the blockchain or system. Deletion is an irreversible destructive action that cannot be undone. While the blast radius is limited to design artifacts (not financial loss or code execution), it qualifies as Destructive rather than Write because the operation cannot be reversed.
From the tool's definition Tool name contains 'delete' and description states 'Delete a token design by ID' — this is an irreversible deletion operation.
Attacks that exploit this kind of access
Delete a token design by ID. 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_creative_design_delete: 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_creative_design_delete 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_creative_design_delete 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_creative_design_delete. 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_creative_design_delete 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 →