Remove a lead from a specific campaign permanently.
AI agents call smartlead_delete_lead_by_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.
This tool meets the Destructive category criteria because it irreversibly deletes data (lead records) and the action cannot be undone. While the blast radius is scoped to a single lead within a campaign (not a wholesale database wipe), permanent deletion of customer data represents high severity.
From the tool's definition The tool 'smartlead_delete_lead_by_campaign' performs a permanent removal of a lead from a campaign. The description explicitly states 'Remove a lead from a specific campaign permanently,' indicating an irreversible deletion operation.
Documented attack patterns abuse exactly the kind of access smartlead_delete_lead_by_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_delete_lead_by_campaign:
{
"version": "1",
"default": "deny",
"hide": [
"smartlead_delete_lead_by_campaign"
]
} smartlead_delete_lead_by_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 a lead from a specific campaign permanently. 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_delete_lead_by_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_delete_lead_by_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_delete_lead_by_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_delete_lead_by_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_delete_lead_by_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.