copy_template · Campaign Monitor MCP: Risk & Policy

WHAT IT DOES

What copy_template does on Campaign Monitor MCP

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

The tool creates or duplicates an existing template resource and associates it with a different client. This is a reversible modification (Write) rather than a destructive operation, as the original template remains and the copy can be deleted. While it modifies the system state by adding new data, it does not execute arbitrary code, delete data irreversibly, or involve financial transactions.

From the tool's definition Tool name 'copy_template' and description 'Copy a template to another client' indicate creation/replication of template data across clients in the email campaign management system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

copy_template Rate-limited

copy_template 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_template": {
      "limits": [
        {
          "counter": "copy_template_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_template

What does the copy_template tool do? +

Copy a template to another client. 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_template? +

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

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

Can I rate-limit copy_template? +

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

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

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