skill_delete
Delete a skill. Only managed and workspace skills can be deleted (not bundled).
This record as markdown: /tools/cowork-os/skill-delete.md
What skill_delete does on CoWork OS
AI agents call skill_delete to permanently remove resources in CoWork OS, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why skill_delete is rated Critical
The tool irreversibly deletes skills from the CoWork OS system. While scoped to certain skill types (managed and workspace, excluding bundled), deletion is inherently irreversible and cannot be undone.
From the tool's definition Tool description states: 'Delete a skill' - an irreversible deletion operation. Qualifier 'Only managed and workspace skills can be deleted' confirms the tool performs permanent removal of data.
Attacks that exploit this kind of access
The rule that runs skill_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For skill_delete, this is the rule to start with:
skill_delete 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 CoWork OS, apply this rule, and every skill_delete call is checked against it from then on.
Questions about skill_delete
Delete a skill. Only managed and workspace skills can be deleted (not bundled). It is categorised as a Destructive tool in the CoWork OS MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CoWork OS MCP server in PolicyLayer and add a rule for skill_delete: 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 CoWork OS. Nothing to install.
skill_delete 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 skill_delete 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 skill_delete. 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.
skill_delete is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
Across the catalogue