Purpose: Create, list, get, update, or remove event definitions in Resend. Events define named triggers that your application sends to start automations. Each event can have an optional schema that validates payload data. Actions: - \
AI agents use manage-events to create or update resources in Email Sending MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Email Sending MCP environment.
The tool performs reversible data modifications (create, update, remove) on event definitions within the Resend email service. While 'remove' appears in the description, it refers to removing event definitions (metadata) rather than irreversibly destroying user data or communications. The primary risk is misconfiguration of automation triggers or disruption of event-driven workflows.
From the tool's definition Tool description states it can "Create, list, get, update, or remove event definitions in Resend." The actions explicitly include create, update, and remove operations on event definitions.
Documented attack patterns abuse exactly the kind of access manage-events gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Email Sending MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for manage-events:
{
"version": "1",
"default": "deny",
"tools": {
"manage-events": {
"limits": [
{
"counter": "manage-events_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage-events stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Purpose: Create, list, get, update, or remove event definitions in Resend. Events define named triggers that your application sends to start automations. Each event can have an optional schema that validates payload data. Actions: - \. It is categorised as a Write tool in the Email Sending MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Email Sending MCP server in PolicyLayer and add a rule for manage-events: 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 Email Sending MCP. Nothing to install.
manage-events 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 manage-events 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 manage-events. 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.
manage-events is provided by the Email Sending MCP server (resend/resend-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 77 Email Sending MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
77 Email Sending MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.