update_site_custom_code

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-custom-code.md

WHAT IT DOES

What update_site_custom_code does on Webcake Storefront

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

This is a Write operation because it creates or modifies site data (custom code) reversibly. While the tool modifies code that could affect site behavior, the changes themselves are not destructive—they can be undone by updating back to previous values. However, severity is 'high' rather than 'medium' because malicious custom code (XSS, credential theft, malware) injected site-wide could compromise all users.

From the tool's definition Tool updates custom code fields (CSS/JS/HTML) for entire site including 'code_before_head', 'code_before_body', 'code_custom_css', and 'code_custom_javascript'.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_site_custom_code Rate-limited

update_site_custom_code 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": {
    "update_site_custom_code": {
      "limits": [
        {
          "counter": "update_site_custom_code_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 update_site_custom_code call is checked against it from then on.

FAQ

Questions about update_site_custom_code

What does the update_site_custom_code tool do? +

Update custom code (CSS/JS) for the entire site. Only sends fields you specify — others remain unchanged. IMPORTANT: Before calling, you MUST read existing code with get_site_custom_code first, then show the user what will change and get explicit confirmation. NEVER update without user approval. - code_before_head: HTML/script inserted before </head> - code_before_body: HTML/script inserted before </body> - code_custom_css: Custom CSS (auto-wrapped in <style>) - code_custom_javascript: Custom JavaScript. 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_custom_code? +

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

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

Can I rate-limit update_site_custom_code? +

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

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

update_site_custom_code 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

generate_and_fetch_code on Stitch MCP Server →aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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