resend_send_batch_emails
AI agents use resend_send_batch_emails to create or update resources in Integrations MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Integrations MCP environment.
Sending emails is a write operation that creates new outbound messages and modifies system state (email queue/logs). While not destructive, this has a 'high' severity due to blast radius: an agent could spam thousands of recipients, damage reputation, violate regulations (CAN-SPAM, GDPR), or be used for phishing.
From the tool's definition Tool name 'resend_send_batch_emails' indicates sending bulk emails through the Resend email service API. The 'send' verb and 'batch' qualifier demonstrate write operations that create/dispatch email messages.
Attacks that exploit this kind of access
resend_send_batch_emails. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Integrations MCP server in PolicyLayer and add a rule for resend_send_batch_emails: 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.
resend_send_batch_emails is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resend_send_batch_emails 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.
Set action: deny in the PolicyLayer policy for resend_send_batch_emails. 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.
resend_send_batch_emails 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →