Remove an email account from a specific campaign.
How to control smartlead_remove_email_account_from_campaign ↓
AI agents call smartlead_remove_email_account_from_campaign to permanently remove resources in SmartLead MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing an email account from a campaign is a destructive action that severs the association between the account and the campaign. This could disrupt ongoing campaign operations, stop email delivery from that account, and may not be easily reversible if campaign state or scheduling depends on that account. The blast radius is high as it could affect live campaigns and ongoing lead communication.
From the tool's definition Remove an email account from a specific campaign
Documented attack patterns abuse exactly the kind of access smartlead_remove_email_account_from_campaign gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SmartLead MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for smartlead_remove_email_account_from_campaign:
{
"version": "1",
"default": "deny",
"hide": [
"smartlead_remove_email_account_from_campaign"
]
} smartlead_remove_email_account_from_campaign disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove an email account from a specific campaign. It is categorised as a Destructive tool in the SmartLead MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SmartLead MCP Server MCP server in PolicyLayer and add a rule for smartlead_remove_email_account_from_campaign: 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 SmartLead MCP Server. Nothing to install.
smartlead_remove_email_account_from_campaign 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 smartlead_remove_email_account_from_campaign 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 smartlead_remove_email_account_from_campaign. 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.
smartlead_remove_email_account_from_campaign is provided by the SmartLead MCP Server MCP server (leadmagic/smartlead-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SmartLead MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
116 SmartLead MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.