Delete a snippet by ID (numeric) or name (string)
AI agents call delete_snippet to permanently remove resources in Iterable 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 snippets from the Iterable platform, which cannot be undone. Deletion of content assets represents a destructive operation with significant blast radius—an AI agent could inadvertently delete widely-used snippet templates, breaking active campaigns or communications. The operation is irreversible and affects marketing infrastructure.
From the tool's definition Tool name 'delete_snippet' combined with description 'Delete a snippet by ID' explicitly indicates irreversible deletion of data. Snippets in marketing platforms are reusable content blocks used across campaigns and communications.
Documented attack patterns abuse exactly the kind of access delete_snippet gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Iterable MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_snippet:
{
"version": "1",
"default": "deny",
"hide": [
"delete_snippet"
]
} delete_snippet disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a snippet by ID (numeric) or name (string). It is categorised as a Destructive tool in the Iterable MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Iterable MCP Server MCP server in PolicyLayer and add a rule for delete_snippet: 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 Iterable MCP Server. Nothing to install.
delete_snippet 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_snippet 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_snippet. 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_snippet is provided by the Iterable MCP Server MCP server (iterable/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Iterable MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
78 Iterable MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.