delete_transactional_email
Permanently delete a saved transactional email template by ID or slug. Use this to retire an obsolete template: the slug stops sending and becomes free to reuse. Already-sent deliveries and their stats are kept, so history and analytics survive the delete. The linked email content stays as a reus...
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/delete-transactional-email.md
What delete_transactional_email does on Sequenzy Mcp
AI agents call delete_transactional_email to permanently remove resources in Sequenzy Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_transactional_email is rated Critical
This tool permanently deletes transactional email templates, which is an irreversible action. While historical delivery records are preserved, the template itself cannot be recovered once deleted. This makes it Destructive rather than Write (which would be reversible).
From the tool's definition "Permanently delete a saved transactional email template by ID or slug" and "the slug stops sending and becomes free to reuse" indicate irreversible deletion of template configuration data.
Attacks that exploit this kind of access
The rule that runs delete_transactional_email safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sequenzy Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_transactional_email, this is the rule to start with:
delete_transactional_email 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 Sequenzy Mcp, apply this rule, and every delete_transactional_email call is checked against it from then on.
Questions about delete_transactional_email
Permanently delete a saved transactional email template by ID or slug. Use this to retire an obsolete template: the slug stops sending and becomes free to reuse. Already-sent deliveries and their stats are kept, so history and analytics survive the delete. The linked email content stays as a reusable template and comes back as. It is categorised as a Destructive tool in the Sequenzy Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sequenzy MCP server in PolicyLayer and add a rule for delete_transactional_email: 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 Sequenzy Mcp. Nothing to install.
delete_transactional_email 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_transactional_email 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_transactional_email. 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_transactional_email is provided by the Sequenzy MCP server (Sequenzy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sequenzy, and thousands of servers like it.
Across the catalogue