delete_subscribers

Delete subscribers by id.

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-subscribers.md

WHAT IT DOES

What delete_subscribers does on Webcake Storefront

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

The tool performs deletion of data (subscribers) which cannot be undone. This is a destructive operation that permanently removes records. While the blast radius is somewhat scoped to subscriber data rather than entire systems, deletion is irreversible and high-impact for a storefront business that relies on subscriber relationships.

From the tool's definition Tool name is 'delete_subscribers' and description states 'Delete subscribers by id' — this irreversibly removes subscriber records from the storefront database.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

delete_subscribers Hidden

delete_subscribers 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_subscribers"
  ]
}

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

FAQ

Questions about delete_subscribers

What does the delete_subscribers tool do? +

Delete subscribers by id. 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_subscribers? +

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

delete_subscribers 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_subscribers? +

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

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

delete_subscribers 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

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

Guides

Govern database agents →Blast radius →Tool call approval →