delete_course
Delete a course by id (also deletes its tracks).
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.
Attacks that exploit this kind of access
The rule that runs delete_course 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_course, this is the rule to start with:
delete_course 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_course call is checked against it from then on.
Questions about delete_course
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.
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.
delete_course 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_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.
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.
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.
Across the catalogue