add_site_languages
Set the full list of enabled languages for the site (used to add, remove, toggle, or change currency — always send the complete updated list). Requires the multilingual app installed.
This record as markdown: /tools/webcake-storefront/add-site-languages.md
What add_site_languages does on Webcake Storefront
AI agents use add_site_languages 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 add_site_languages is rated Medium
This tool creates or modifies site language and currency settings. While these changes are reversible (languages and currencies can be re-configured later), they affect storefront functionality and customer experience. Misuse could render a site inaccessible in certain languages or break pricing for specific regions.
From the tool's definition Tool description states it 'Set[s] the full list of enabled languages for the site' and can 'add, remove, toggle, or change currency'. These are modifying operations that alter site configuration reversibly.
Attacks that exploit this kind of access
The rule that runs add_site_languages 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 add_site_languages, this is the rule to start with:
add_site_languages 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 add_site_languages call is checked against it from then on.
Questions about add_site_languages
Set the full list of enabled languages for the site (used to add, remove, toggle, or change currency — always send the complete updated list). Requires the multilingual app installed. 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 add_site_languages: 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.
add_site_languages 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 add_site_languages 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 add_site_languages. 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.
add_site_languages 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