deactivate_webhook · Campaign Monitor MCP: Risk & Policy

WHAT IT DOES

What deactivate_webhook does on Campaign Monitor MCP

AI agents use deactivate_webhook to create or update resources in Campaign Monitor MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Campaign Monitor MCP environment.

WHY IT NEEDS A POLICY

Why deactivate_webhook needs a policy

Deactivating a webhook disables an existing integration but does not delete it — it is a reversible state change (can be reactivated), making it a Write operation rather than Destructive. Misuse could disrupt event-driven workflows, hence medium severity.

From the tool's definition Deactivate a webhook for a subscriber list

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deactivate_webhook Rate-limited

deactivate_webhook 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deactivate_webhook": {
      "limits": [
        {
          "counter": "deactivate_webhook_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Campaign Monitor MCP, so you can run agents against it safely.

FAQ

Questions about deactivate_webhook

What does the deactivate_webhook tool do? +

Deactivate a webhook for a subscriber list. It is categorised as a Write tool in the Campaign Monitor MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on deactivate_webhook? +

Register the Campaign Monitor MCP server in PolicyLayer and add a rule for deactivate_webhook: 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 Campaign Monitor MCP. Nothing to install.

What risk level is deactivate_webhook? +

deactivate_webhook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit deactivate_webhook? +

Yes. Add a rate_limit block to the deactivate_webhook 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.

How do I block deactivate_webhook completely? +

Set action: deny in the PolicyLayer policy for deactivate_webhook. 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.

What MCP server provides deactivate_webhook? +

deactivate_webhook is provided by the Campaign Monitor MCP server (pauliowest/cmon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.