Critical Risk →

org_skill_delete

Delete a shared organization skill from Shellgate

How to control org_skill_delete ↓

What org_skill_delete does on Shellgate

AI agents call org_skill_delete to permanently remove resources in Shellgate — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why org_skill_delete needs a policy

This tool performs an irreversible deletion operation on shared organizational data. Deletion cannot be undone and represents a destructive action. The 'shared' nature means the impact affects multiple users/teams.

From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a shared organization skill from Shellgate', indicating irreversible removal of data.

Documented attack patterns abuse exactly the kind of access org_skill_delete gives an agent:

How to control org_skill_delete

PolicyLayer is an MCP gateway — it sits between your AI agents and Shellgate, and nothing reaches the server without passing your rules. This is the rule we recommend for org_skill_delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "org_skill_delete"
  ]
}

org_skill_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Shellgate — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about org_skill_delete

What does the org_skill_delete tool do? +

Delete a shared organization skill from Shellgate. It is categorised as a Destructive tool in the Shellgate 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 org_skill_delete? +

Register the Shellgate MCP server in PolicyLayer and add a rule for org_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 Shellgate. Nothing to install.

What risk level is org_skill_delete? +

org_skill_delete 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 org_skill_delete? +

Yes. Add a rate_limit block to the org_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.

How do I block org_skill_delete completely? +

Set action: deny in the PolicyLayer policy for org_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.

What MCP server provides org_skill_delete? +

org_skill_delete is provided by the Shellgate MCP server (matthiastjong/shellgate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Shellgate tool call.

Start from Shellgate, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

31 Shellgate tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.