jm_remove_repo

Remove a repository from JarvisManager.

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/jm-remove-repo.md

WHAT IT DOES

What jm_remove_repo does on CLIO Adios

AI agents call jm_remove_repo 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 jm_remove_repo is rated Critical

This tool deletes repository data from JarvisManager. Deletion of a repository is a destructive operation with no recovery mechanism. The blast radius is high as an AI agent could remove critical repositories needed for data analysis or collaboration. This falls squarely into the Destructive category (irreversibly removes data) rather than Write (reversible modification).

From the tool's definition 'Remove a repository from JarvisManager' — the verb 'remove' indicates deletion of a repository, which is irreversible and cannot be undone.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs jm_remove_repo 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 jm_remove_repo, this is the rule to start with:

jm_remove_repo Hidden

jm_remove_repo 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": [
    "jm_remove_repo"
  ]
}

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 jm_remove_repo call is checked against it from then on.

FAQ

Questions about jm_remove_repo

What does the jm_remove_repo tool do? +

Remove a repository from JarvisManager. 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 jm_remove_repo? +

Register the CLIO Adios MCP server in PolicyLayer and add a rule for jm_remove_repo: 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 jm_remove_repo? +

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

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

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

jm_remove_repo 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 →delete_git_repo 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 →