send_mail
Trigger a CMS automation to send an email (same endpoint @webcake/app/automation sendMail uses). Requires the automation_id — get it from list_automations.
This record as markdown: /tools/webcake-storefront/send-mail.md
What send_mail does on Webcake Storefront
AI agents invoke send_mail to trigger actions in Webcake Storefront. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why send_mail is rated High
This tool triggers an external operation (sending an email via a CMS automation) whose effects depend on the arguments provided (automation_id, likely recipients and content). Sending email is an external side-effect that cannot be undone once dispatched. It falls under Execute rather than Write because it triggers an external operation (email delivery) rather than simply creating/modifying internal data.
From the tool's definition Trigger a CMS automation to send an email
Attacks that exploit this kind of access
The rule that runs send_mail safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Webcake Storefront, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_mail, this is the rule to start with:
send_mail stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every send_mail call is checked against it from then on.
Questions about send_mail
Trigger a CMS automation to send an email (same endpoint @webcake/app/automation sendMail uses). Requires the automation_id — get it from list_automations. It is categorised as a Execute tool in the Webcake Storefront MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for send_mail: 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 Webcake Storefront. Nothing to install.
send_mail is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_mail 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 send_mail. 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.
send_mail is provided by the Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Webcake Storefront, and thousands of servers like it.
Across the catalogue