add_section
Append a section to an EXISTING page
This record as markdown: /tools/webcake-storefront/add-section.md
What add_section does on Webcake Storefront
AI agents use add_section 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 add_section is rated Medium
This tool modifies page structure by adding a new section to an existing page. This is a Create/Write operation within the page authoring workflow of the storefront builder. It is reversible (the section could be removed), so it does not qualify as Destructive. It does not execute arbitrary code, retrieve data only, move money, or trigger external operations—it simply modifies the page data structure.
From the tool's definition Tool description explicitly states 'Append a section to an EXISTING page'. The verb 'append' indicates modification of existing data (adding a section to a page structure).
Attacks that exploit this kind of access
The rule that runs add_section 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 add_section, this is the rule to start with:
add_section 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every add_section call is checked against it from then on.
Questions about add_section
Append a section to an EXISTING page. 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.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for add_section: 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.
add_section is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_section 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.
Set action: deny in the PolicyLayer policy for add_section. 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.
add_section 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.
This server
Across the catalogue