update_site_slug

Change the site

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-slug.md

What update_site_slug does on Webcake Storefront

AI agents use update_site_slug 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_slug is rated Medium

This tool modifies site metadata (the URL slug) reversibly. It is a Write operation rather than Destructive because slug changes can typically be reverted. The severity is high because changing a site slug on a live storefront could disrupt customer access, SEO, and bookmarks if done improperly, though the change itself is not irreversible.

From the tool's definition Tool name 'update_site_slug' and description 'Change the site' indicate modification of site configuration. The slug is a critical URL identifier for a storefront, and changing it affects the site's public-facing identity and routing.

Questions about update_site_slug

What does the update_site_slug tool do? +

Change the site. 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_slug? +

Register the Webcake Storefront MCP server in PolicyLayer and add a rule for update_site_slug: 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_slug? +

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

Can I rate-limit update_site_slug? +

Yes. Add a rate_limit block to the update_site_slug 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_slug completely? +

Set action: deny in the PolicyLayer policy for update_site_slug. 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_slug? +

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