delete_global_section
Delete a global section (Header/Footer/block) and remove its node from every page source. Two-step safety: dry_run=true (default) shows which pages would change; dry_run=false performs the atomic save.
This record as markdown: /tools/webcake-storefront/delete-global-section.md
What delete_global_section does on Webcake Storefront
AI agents call delete_global_section to permanently remove resources in Webcake Storefront, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_global_section is rated Critical
The tool permanently deletes data (a global section) and modifies all dependent pages in a single atomic operation. This cannot be undone and has broad blast radius across the storefront. Although it includes a dry_run safety mechanism, the actual delete operation (dry_run=false) is destructive. This is more severe than Write (reversible modifications) and qualifies as Destructive per the schema definition.
From the tool's definition Tool name 'delete_global_section' and description explicitly states 'Delete a global section' and 'remove its node from every page source.' This is an irreversible deletion affecting multiple pages atomically.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs delete_global_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 delete_global_section, this is the rule to start with:
delete_global_section is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every delete_global_section call is checked against it from then on.
Questions about delete_global_section
Delete a global section (Header/Footer/block) and remove its node from every page source. Two-step safety: dry_run=true (default) shows which pages would change; dry_run=false performs the atomic save. It is categorised as a Destructive tool in the Webcake Storefront MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for delete_global_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.
delete_global_section is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_global_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 delete_global_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.
delete_global_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.
Across the catalogue