Medium Risk

send-broadcast

Send a broadcast campaign to audience

Risk signalsMass sends emails to entire audience

Part of the Resend server.

send-broadcast can modify Resend data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE RESEND →

Free to start. No card required.

AI agents use send-broadcast to create or modify resources in Resend. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call send-broadcast repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Resend.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "send-broadcast": {
      "limits": [
        {
          "counter": "send-broadcast_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Resend policy for all 44 tools.

Get this rule live on your own Resend server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY RESEND →

View all 44 tools →

These attack patterns abuse exactly the kind of access send-broadcast gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so send-broadcast only ever does what you allow.

SECURE RESEND →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the send-broadcast tool do? +

Send a broadcast campaign to audience. It is categorised as a Write tool in the Resend MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on send-broadcast? +

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

What risk level is send-broadcast? +

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

Can I rate-limit send-broadcast? +

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

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

send-broadcast is provided by the Resend MCP server (@resend-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Resend tool call.

Deterministic rules across all 44 Resend tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.