update_site_settings
Update general site settings. The \
This record as markdown: /tools/webcake-storefront/update-site-settings.md
What update_site_settings does on Webcake Storefront
AI agents use update_site_settings 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 update_site_settings is rated Medium
This tool modifies site-level configuration and settings, which are reversible changes (Write category). However, severity is high because updating site settings can have broad impact across the storefront—affecting store behavior, customer experience, and potentially integrations. An agent given incorrect instructions could misconfigure critical site parameters, necessitating manual restoration.
From the tool's definition Tool name 'update_site_settings' and description 'Update general site settings' indicate modification of site configuration data. The incomplete description ('The \') provides limited detail, but the verb 'update' clearly indicates write/modification action.
Attacks that exploit this kind of access
The rule that runs update_site_settings 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 update_site_settings, this is the rule to start with:
update_site_settings 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 update_site_settings call is checked against it from then on.
Questions about update_site_settings
Update general site settings. The \. 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 update_site_settings: 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.
update_site_settings 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 update_site_settings 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 update_site_settings. 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.
update_site_settings 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