postmark_send_batch · Integrations MCP: Risk & Policy

WHAT IT DOES

What postmark_send_batch does on Integrations MCP

AI agents invoke postmark_send_batch to trigger actions in Integrations 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 postmark_send_batch needs a policy

Sending a batch of emails is an external operation with real-world effects (delivering messages to recipients). The description is empty, lowering confidence, but the name strongly implies triggering email delivery at scale. This falls under Execute (triggering external operations) with high severity since misuse could result in mass unsolicited email sends to many recipients.

From the tool's definition Tool name 'postmark_send_batch' — 'send_batch' implies sending a batch of emails via Postmark email service.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

postmark_send_batch Rate-limited

postmark_send_batch 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": {
    "postmark_send_batch": {
      "limits": [
        {
          "counter": "postmark_send_batch_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 Integrations MCP, so you can run agents against it safely.

FAQ

Questions about postmark_send_batch

What does the postmark_send_batch tool do? +

postmark_send_batch. It is categorised as a Execute tool in the Integrations 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 postmark_send_batch? +

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

What risk level is postmark_send_batch? +

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

Can I rate-limit postmark_send_batch? +

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

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

postmark_send_batch is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.