stop_campaign
Stop an active or paused campaign permanently — cannot be resumed.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/stop-campaign.md
What stop_campaign does on Max MCP Server
AI agents call stop_campaign to permanently remove resources in Max MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why stop_campaign is rated Critical
This tool irreversibly terminates a campaign with no undo capability. While not deleting data in a database sense, it permanently disables a business operation (sales campaign) that cannot be restored, making it destructive rather than merely a write operation.
From the tool's definition Tool description states 'Stop an active or paused campaign permanently — cannot be resumed.' The word 'permanently' and explicit statement that it 'cannot be resumed' indicate an irreversible action that destroys the campaign's active state.
Attacks that exploit this kind of access
The rule that runs stop_campaign safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stop_campaign, this is the rule to start with:
stop_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 Max MCP Server, apply this rule, and every stop_campaign call is checked against it from then on.
Questions about stop_campaign
Stop an active or paused campaign permanently — cannot be resumed. It is categorised as a Destructive tool in the Max MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for stop_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 Max MCP Server. Nothing to install.
stop_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 stop_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 stop_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.
stop_campaign is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
Across the catalogue