Delete a sending domain
AI agents call delete-sending-domain 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.
Deleting a sending domain is a destructive action that cannot be automatically undone. It removes email sending capability for that domain and may affect ongoing email operations, deliverability, and configurations. This qualifies as Destructive (irreversible deletion) rather than Write (reversible modification).
From the tool's definition Tool name is 'delete-sending-domain' and description explicitly states 'Delete a sending domain'. The verb 'delete' combined with the permanent removal of email infrastructure indicates an irreversible operation.
Attacks that exploit this kind of access
Delete a sending domain. 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-sending-domain: 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-sending-domain 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-sending-domain 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-sending-domain. 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-sending-domain 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 →