remove_pkg

Delete a package only when JARVIS-CD provides destructive removal semantics.

SERVERCLIO Adios SOURCEpypi:clio-kit

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/io-github-iowarp-adios-mcp/remove-pkg.md

WHAT IT DOES

What remove_pkg does on CLIO Adios

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

RISK

Why remove_pkg is rated Critical

An AI agent that decides to call remove_pkg doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from CLIO Adios is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_pkg safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CLIO Adios, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_pkg, this is the rule to start with:

remove_pkg Hidden

remove_pkg is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_pkg"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CLIO Adios, apply this rule, and every remove_pkg call is checked against it from then on.

FAQ

Questions about remove_pkg

What does the remove_pkg tool do? +

Delete a package only when JARVIS-CD provides destructive removal semantics. It is categorised as a Destructive tool in the CLIO Adios 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 remove_pkg? +

Register the CLIO Adios MCP server in PolicyLayer and add a rule for remove_pkg: 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 CLIO Adios. Nothing to install.

What risk level is remove_pkg? +

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

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

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

remove_pkg is provided by the CLIO Adios MCP server (pypi:clio-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CLIO Adios, and thousands of servers like it.

This server

All 204 CLIO Adios tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →