delete_global_source

Delete a global source and its published version

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/delete-global-source.md

WHAT IT DOES

What delete_global_source does on Webcake Storefront

AI agents call delete_global_source 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 delete_global_source is rated Critical

This tool permanently removes a global source and its published version from the storefront, which cannot be undone. Deletion is irreversible data loss, making it Destructive rather than Write. The blast radius is high because an AI agent could inadvertently delete critical storefront assets (templates, reusable components, or configuration), disrupting the storefront's functionality.

From the tool's definition Tool name contains 'delete' and description states 'Delete a global source and its published version' — irreversible deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

delete_global_source Hidden

delete_global_source 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": [
    "delete_global_source"
  ]
}

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 delete_global_source call is checked against it from then on.

FAQ

Questions about delete_global_source

What does the delete_global_source tool do? +

Delete a global source and its published version. 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 delete_global_source? +

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

delete_global_source 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 delete_global_source? +

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

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

delete_global_source 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

delete_by_source on MCP RAG Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →