delete_course

Delete a course by id (also deletes its tracks).

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

What delete_course does on Webcake Storefront

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

This tool performs an irreversible delete operation on a course and its dependent data (tracks). According to the classification rules, destructive actions that cannot be undone (delete, drop, purge) take highest precedence over write operations. The blast radius is significant because deleting a course removes all associated content and metadata, affecting customers, sales, and storefront organization.

From the tool's definition The tool description explicitly states 'Delete a course by id (also deletes its tracks),' which indicates irreversible deletion of data. The cascading deletion of associated tracks compounds the destructive impact.

Questions about delete_course

What does the delete_course tool do? +

Delete a course by id (also deletes its tracks). 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_course? +

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

delete_course 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_course? +

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

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

delete_course 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Webcake Storefront's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.