update_cms_file

What update_cms_file does on Webcake Storefront

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

This tool creates or modifies data reversibly by updating CMS file code. While not destructive (no deletion), it carries high severity because unauthorized updates to CMS files could inject malicious code, alter site logic, deface content, or compromise the storefront's functionality and security. The blast radius includes potential site defacement, customer data exposure via injected code, and business disruption.

From the tool's definition 'Update the code content of an existing CMS file' — directly modifies file content, a reversible Write operation. The term 'update' confirms modification rather than deletion, and 'code content' indicates it alters executable or structural assets.

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

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

Questions about update_cms_file