Delete a sending domain from a client
AI agents call delete_sending_domain to permanently remove resources in Campaign Monitor MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a sending domain is an irreversible operation that removes email infrastructure. While not as critical as deleting subscriber data or financial records, it prevents the client from sending emails and cannot be undone without reconfiguration. This qualifies as Destructive rather than Write because the operation cannot be reversed (domain deletion is permanent).
From the tool's definition Tool name contains 'delete' and description states 'Delete a sending domain from a client'. The action irreversibly removes configuration that enables email delivery.
Attacks that exploit this kind of access
Delete a sending domain from a client. It is categorised as a Destructive tool in the Campaign Monitor MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Campaign Monitor 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 Campaign Monitor MCP. 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 Campaign Monitor MCP server (pauliowest/cmon-mcp). 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 →