Delete an existing email template
AI agents call delete-template to permanently remove resources in Mcp Mailtrap — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes an email template from the Mailtrap system. Deletion is irreversible and cannot be undone through normal operations. While the blast radius is scoped to templates (not all data), accidental or malicious deletion of templates could disrupt email communication workflows. This is classified as Destructive rather than Write because the operation cannot be reversed.
From the tool's definition Tool name and description: 'Delete an existing email template' - the verb 'delete' combined with 'existing' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete an existing email template. It is categorised as a Destructive tool in the Mcp Mailtrap MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Mailtrap 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 Mcp Mailtrap. 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 Mcp Mailtrap MCP server (mcp-mailtrap). 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 →