Purpose: Get details of a specific automation (with its workflow) or list all automations. Modes: - With \
AI agents call get-automation to retrieve information from Email Sending MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves automation metadata and workflow information without creating, modifying, deleting, executing external operations, or committing financial transactions. It is a read-only query operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'Get details of a specific automation' and 'list all automations' — purely retrievals with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get-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 get-automation:
{
"version": "1",
"default": "deny",
"tools": {
"get-automation": {}
}
}get-automation is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Purpose: Get details of a specific automation (with its workflow) or list all automations. Modes: - With \. It is categorised as a Read tool in the Email Sending MCP MCP Server, which means it retrieves data without modifying state.
Register the Email Sending MCP server in PolicyLayer and add a rule for get-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.
get-automation is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-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 get-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.
get-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.