Permanently delete a contact list by ID.
AI agents call delete-contact-list 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 irreversibly deletes data (a contact list) with no undo capability. While not as severe as financial operations, permanent deletion of user contact data represents a high-severity destructive action that could cause significant harm if invoked maliciously or by mistake, particularly in a bulk email/CRM context where contact lists are critical business assets.
From the tool's definition Tool description explicitly states "Permanently delete a contact list by ID" - the word "delete" combined with "permanently" indicates irreversible data destruction.
Attacks that exploit this kind of access
Permanently delete a contact list by ID. 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-contact-list: 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-contact-list 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-contact-list 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-contact-list. 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-contact-list 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 →