rename_site

Rename the site (display name).

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/rename-site.md

WHAT IT DOES

What rename_site does on Webcake Storefront

AI agents use rename_site 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.

RISK

Why rename_site is rated Medium

This tool creates or modifies data reversibly by changing the site's display name. It does not delete data, execute code, move money, or perform irreversible operations. The change can be undone by renaming again, making it a Write operation with low severity since renaming metadata has minimal blast radius and no cascading side effects.

From the tool's definition The tool 'rename_site' updates the site's display name, which is a reversible modification to site metadata. The description explicitly states it renames the site (display name), confirming a write operation without deletion or irreversible effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rename_site 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 rename_site, this is the rule to start with:

rename_site Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_site": {
      "limits": [
        {
          "counter": "rename_site_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every rename_site call is checked against it from then on.

FAQ

Questions about rename_site

What does the rename_site tool do? +

Rename the site (display name). 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 rename_site? +

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

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

Can I rate-limit rename_site? +

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

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

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

KEEP EXPLORING

More on Webcake Storefront, and thousands of servers like it.

This server

All 287 Webcake Storefront tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →