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.

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about send_mail

What does the send_mail tool do? +

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.

How do I enforce a policy on send_mail? +

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.

What risk level is send_mail? +

send_mail is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit send_mail? +

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.

How do I block send_mail completely? +

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.

What MCP server provides send_mail? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Webcake Storefront's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.