AI agents use update-automation 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.
This tool creates or modifies data (automation rules/workflows) reversibly—automations can be updated again or disabled without permanent deletion. This qualifies as Write rather than Execute because it changes configuration metadata rather than directly triggering email sends. However, misuse could enable unauthorized automation of email campaigns affecting many recipients, warranting medium severity.
From the tool's definition Tool name 'update-automation' and description 'Update an automation' indicate modification of existing automation configurations. In an email sending system, automations control email workflows and triggers.
Documented attack patterns abuse exactly the kind of access update-automation 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 update-automation:
{
"version": "1",
"default": "deny",
"tools": {
"update-automation": {
"limits": [
{
"counter": "update-automation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-automation 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: Update an automation. 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 update-automation: 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.
update-automation 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 update-automation 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 update-automation. 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.
update-automation 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.