AI agents call fluentcrm_delete_campaign to permanently remove resources in FluentCRM MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Campaign deletion is an irreversible destructive action that cannot be undone. Once deleted, the campaign and its associated data (scheduling, performance metrics, audience configurations) are lost. This represents a high blast radius if triggered unintentionally by an AI agent, as it could destroy active marketing campaigns and their historical records.
From the tool's definition Tool name explicitly contains 'delete_campaign' and description states 'Usuwa kampanię' (Polish for 'Deletes campaign'). This irreversibly removes a campaign object from the system.
Documented attack patterns abuse exactly the kind of access fluentcrm_delete_campaign gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and FluentCRM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for fluentcrm_delete_campaign:
{
"version": "1",
"default": "deny",
"hide": [
"fluentcrm_delete_campaign"
]
}fluentcrm_delete_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.
Usuwa kampanię. It is categorised as a Destructive tool in the FluentCRM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FluentCRM MCP Server MCP server in PolicyLayer and add a rule for fluentcrm_delete_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 FluentCRM MCP Server. Nothing to install.
fluentcrm_delete_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 fluentcrm_delete_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 fluentcrm_delete_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.
fluentcrm_delete_campaign is provided by the FluentCRM MCP Server MCP server (netflyapp/fluentcrm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from FluentCRM 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.
36 FluentCRM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.