update_site_settings

Update general site settings. The \

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp
Medium RISK CLASS
Category Write
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/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.

Questions about update_site_settings

What does the update_site_settings tool do? +

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.

How do I enforce a policy on update_site_settings? +

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.

What risk level is update_site_settings? +

update_site_settings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_site_settings? +

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.

How do I block update_site_settings completely? +

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.

What MCP server provides update_site_settings? +

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.

// 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.