restore_campaign
Restore a previously deleted campaign.
This record as markdown: /tools/io-favcrm-favcrm/restore-campaign.md
What restore_campaign does on FavCRM
AI agents use restore_campaign to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
campaignId | string | Yes | Campaign ID |
Parameters from the server's own tool schema.
Why restore_campaign is rated Medium
This tool modifies data by restoring a deleted campaign to an active state, which is a reversible write operation (the campaign can be deleted again). It is not destructive because the action is undoable and does not permanently erase data. It lacks the irreversibility required for Destructive classification.
From the tool's definition Tool name 'restore_campaign' and description 'Restore a previously deleted campaign' indicate recovery/modification of campaign data that was in a deleted state.
Attacks that exploit this kind of access
The rule that runs restore_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 restore_campaign, this is the rule to start with:
restore_campaign stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every restore_campaign call is checked against it from then on.
Questions about restore_campaign
Restore a previously deleted campaign. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
restore_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 restore_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.
restore_campaign is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the restore_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 restore_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.
restore_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.
This server
Across the catalogue