jm_cd

Change current Jarvis pipeline context.

SERVERCLIO Adios SOURCEpypi:clio-kit

High RISK CLASS

Category Execute

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-cd.md

WHAT IT DOES

What jm_cd does on CLIO Adios

AI agents invoke jm_cd to trigger actions in CLIO Adios. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why jm_cd is rated High

Changing pipeline context is an active operation that modifies the runtime environment/state of the Jarvis pipeline system. It triggers an external operation (context switch) that affects subsequent tool calls and pipeline execution, placing it in the Execute category. The blast radius is medium as misconfiguring the pipeline context could cause subsequent operations to run in the wrong environment.

From the tool's definition Change current Jarvis pipeline context

Attacks that exploit this kind of access

RECOMMENDED RULE

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

jm_cd Rate-limited

jm_cd stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_cd": {
      "limits": [
        {
          "counter": "jm_cd_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about jm_cd

What does the jm_cd tool do? +

Change current Jarvis pipeline context. It is categorised as a Execute tool in the CLIO Adios MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on jm_cd? +

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

jm_cd is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit jm_cd? +

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

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

jm_cd 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →