resend_transactional_message · Campaign Monitor MCP

WHAT IT DOES

What resend_transactional_message does on Campaign Monitor MCP

AI agents invoke resend_transactional_message 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 resend_transactional_message needs a policy

This tool triggers an external operation — sending an email message — which constitutes an action with real-world effects (email delivery to recipients). It doesn't create or modify data in a reversible storage sense, nor delete data, nor move money. It executes an email send operation via the Campaign Monitor API, making Execute the most appropriate category.

From the tool's definition Resend a previously sent transactional message

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resend_transactional_message Rate-limited

resend_transactional_message 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": {
    "resend_transactional_message": {
      "limits": [
        {
          "counter": "resend_transactional_message_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 resend_transactional_message

What does the resend_transactional_message tool do? +

Resend a previously sent transactional message. 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 resend_transactional_message? +

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

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

Can I rate-limit resend_transactional_message? +

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

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

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