Permanently delete a contact field definition by ID.
AI agents call delete-contact-field 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 field definition) that cannot be easily recovered. While the blast radius is contained to field definitions rather than individual contacts or financial data, permanent deletion of schema elements that other contacts may depend on qualifies as Destructive.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Permanently delete a contact field definition by ID'. The use of 'Permanently' indicates irreversible removal of data.
Attacks that exploit this kind of access
Permanently delete a contact field definition 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-field: 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-field 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-field 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-field. 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-field 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 →