jm_add_repo

Add a repository to JarvisManager.

SERVERCLIO Adios SOURCEpypi:clio-kit

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-iowarp-adios-mcp/jm-add-repo.md

WHAT IT DOES

What jm_add_repo does on CLIO Adios

AI agents use jm_add_repo to create or update resources in CLIO Adios, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CLIO Adios environment.

RISK

Why jm_add_repo is rated Medium

Adding a repository to a package/repository manager constitutes creating a new configuration entry that reversibly modifies system state. While this could enable downstream execution of code from untrusted sources, the tool itself performs a write operation (adding metadata/configuration) rather than executing code or destructively removing data.

From the tool's definition Tool performs 'Add a repository' which is a create/modify operation on configuration state in JarvisManager. The verb 'add' indicates data creation without irreversible deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

jm_add_repo Rate-limited

jm_add_repo stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jm_add_repo": {
      "limits": [
        {
          "counter": "jm_add_repo_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about jm_add_repo

What does the jm_add_repo tool do? +

Add a repository to JarvisManager. It is categorised as a Write tool in the CLIO Adios MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on jm_add_repo? +

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

jm_add_repo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit jm_add_repo? +

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

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

jm_add_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 →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb →add_video on Mcptube Vision → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →