send_classic_email · Campaign Monitor MCP: Risk & Policy

WHAT IT DOES

What send_classic_email does on Campaign Monitor MCP

AI agents invoke send_classic_email to trigger actions in Campaign Monitor MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why send_classic_email needs a policy

Sending an email is an external operation with real-world side effects (delivering messages to recipients). It is not purely a write (data storage) operation but an execution of an external communication action. Misuse could result in sending spam, phishing, or unauthorized emails to recipients at scale, making the blast radius high.

From the tool's definition 'Send a one-off transactional email via Campaign Monitor' — triggers an external email delivery operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_classic_email Rate-limited

send_classic_email stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_classic_email": {
      "limits": [
        {
          "counter": "send_classic_email_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 send_classic_email

What does the send_classic_email tool do? +

Send a one-off transactional email via Campaign Monitor. It is categorised as a Execute tool in the Campaign Monitor MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on send_classic_email? +

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

send_classic_email is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit send_classic_email? +

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

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

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