delete_campaign
Delete a campaign. Only allowed in DRAFT status; sent campaigns are kept for audit history.
This record as markdown: /tools/io-favcrm-favcrm/delete-campaign.md
What delete_campaign does on FavCRM
AI agents call delete_campaign to permanently remove resources in FavCRM, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
campaignId | string | Yes | Campaign ID |
Parameters from the server's own tool schema.
Why delete_campaign is rated Critical
This tool permanently removes campaign data from the system. Although the description notes that only DRAFT campaigns can be deleted (and sent campaigns are retained for audit), the core operation is destructive — once a draft campaign is deleted, it cannot be recovered. This is an irreversible action affecting business data in a CRM context, warranting the Destructive category.
From the tool's definition Tool name is 'delete_campaign' with description stating 'Delete a campaign.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_campaign safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_campaign, this is the rule to start with:
delete_campaign is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every delete_campaign call is checked against it from then on.
Questions about delete_campaign
Delete a campaign. Only allowed in DRAFT status; sent campaigns are kept for audit history. It is categorised as a Destructive tool in the FavCRM MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_campaign accepts 1 parameter: campaignId. Required: campaignId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for 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 FavCRM. Nothing to install.
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 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 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.
delete_campaign is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
Across the catalogue