save_email_templates
Create/update the transactional email templates. Each block is { title, content, status }.
This record as markdown: /tools/webcake-storefront/save-email-templates.md
What save_email_templates does on Webcake Storefront
AI agents use save_email_templates to create or update resources in Webcake Storefront, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Webcake Storefront environment.
Why save_email_templates is rated Medium
The tool creates or updates email templates, which is a reversible Write operation. Transactional emails are critical to customer communication, so misuse could send incorrect emails to customers (medium severity), but the templates themselves can be edited or reverted. This does not rise to Execute (no code execution), Destructive (data can be modified again), or Financial (no payment/transaction handling).
From the tool's definition Tool description states "Create/update the transactional email templates", which are operations that modify data reversibly without deleting or executing external code.
Attacks that exploit this kind of access
The rule that runs save_email_templates 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 save_email_templates, this is the rule to start with:
save_email_templates 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every save_email_templates call is checked against it from then on.
Questions about save_email_templates
Create/update the transactional email templates. Each block is { title, content, status }. It is categorised as a Write tool in the Webcake Storefront MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for save_email_templates: 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.
save_email_templates 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 save_email_templates 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 save_email_templates. 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.
save_email_templates 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.
This server
Across the catalogue