clear_page_draft

Delete a local page draft (does NOT delete any backend page already created from it).

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/webcake-storefront/clear-page-draft.md

WHAT IT DOES

What clear_page_draft does on Webcake Storefront

AI agents call clear_page_draft 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.

RISK

Why clear_page_draft is rated Critical

The tool deletes data (page drafts) without the ability to undo or recover the deleted content. Although it clarifies that backend pages are unaffected, the deletion of the draft itself is an irreversible destructive action.

From the tool's definition 'Delete a local page draft' — the tool explicitly performs deletion of draft content, which is irreversible.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

clear_page_draft Hidden

clear_page_draft is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_page_draft"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every clear_page_draft call is checked against it from then on.

FAQ

Questions about clear_page_draft

What does the clear_page_draft tool do? +

Delete a local page draft (does NOT delete any backend page already created from it). 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.

How do I enforce a policy on clear_page_draft? +

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

clear_page_draft is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_page_draft? +

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

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

clear_page_draft 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 → Critical-risk tools on this server →

Across the catalogue

clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP →clear_spam_box on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →