copy_journey · Campaign Monitor MCP: Risk & Policy

WHAT IT DOES

What copy_journey does on Campaign Monitor MCP

AI agents use copy_journey 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 copy_journey needs a policy

The copy_journey tool creates new journey resources by duplicating existing journeys to specified clients and lists. This is a Write operation because it creates/duplicates data reversibly. It is not Destructive (no irreversible deletion), not Execute (no arbitrary code/commands), not Financial (no money movement), and not Read (has side effects of creating new resources).

From the tool's definition Tool name 'copy_journey' and description 'Copy a journey to a specified client and list' indicate creation of a new journey resource by duplicating an existing one. This is a reversible data modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

copy_journey Rate-limited

copy_journey 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": {
    "copy_journey": {
      "limits": [
        {
          "counter": "copy_journey_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 copy_journey

What does the copy_journey tool do? +

Copy a journey to a specified client and 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 copy_journey? +

Register the Campaign Monitor MCP server in PolicyLayer and add a rule for copy_journey: 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 copy_journey? +

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

Can I rate-limit copy_journey? +

Yes. Add a rate_limit block to the copy_journey 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 copy_journey completely? +

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

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