update_page_content

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-page-content.md

WHAT IT DOES

What update_page_content does on Webcake Storefront

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

This tool creates or modifies page content for a storefront builder, fitting the Write category—it alters data but the changes are reversible (content can be updated again). Severity is medium because while it affects customer-facing storefront pages, the built-in safeguard requiring explicit user confirmation before execution mitigates risk of accidental misuse by an AI agent.

From the tool's definition Tool description explicitly states 'Create/update page content' which are write operations that modify data reversibly. The instruction to read existing content first and get user confirmation before updating indicates this modifies storefront pages.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_page_content Rate-limited

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

FAQ

Questions about update_page_content

What does the update_page_content tool do? +

Create/update page content for a specific language. IMPORTANT: Before calling, you MUST read existing content with list_page_contents first, then show the user what will change and get explicit confirmation. NEVER update without user approval. 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_page_content? +

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

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

Can I rate-limit update_page_content? +

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

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

update_page_content 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

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 →