delete_category
Delete a category from the Thinkific site.
This record as markdown: /tools/ackbarguppi-ai-thinkific-mcp/delete-category.md
What delete_category does on Thinkific MCP Server
AI agents call delete_category to permanently remove resources in Thinkific MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_category is rated Critical
The tool irreversibly removes a category, which cannot be undone. Deletion of a category may cascade to affect associated courses, products, or content, making this a high-severity destructive action. An AI agent misusing this tool could permanently remove important organizational structures and the data they contain.
From the tool's definition delete_category: Delete a category from the Thinkific site.
Attacks that exploit this kind of access
The rule that runs delete_category safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Thinkific MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_category, this is the rule to start with:
delete_category 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 Thinkific MCP Server, apply this rule, and every delete_category call is checked against it from then on.
Questions about delete_category
Delete a category from the Thinkific site. It is categorised as a Destructive tool in the Thinkific MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Thinkific MCP Server MCP server in PolicyLayer and add a rule for delete_category: 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 Thinkific MCP Server. Nothing to install.
delete_category 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_category 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_category. 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_category is provided by the Thinkific MCP Server MCP server (ackbarguppi-ai/thinkific-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Thinkific MCP Server, and thousands of servers like it.
Across the catalogue