jm_reset

Reset JarvisManager (destroy all pipelines and data).

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

WHAT IT DOES

What jm_reset does on CLIO Adios

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

The tool performs a destructive operation that cannot be undone. The language "destroy all pipelines and data" indicates permanent deletion of resources. While the server context suggests scientific data management, the tool's explicit destructive capability and broad scope (affecting all pipelines and data simultaneously) poses a critical risk if invoked by an unauthorized or confused AI agent.

From the tool's definition Tool description explicitly states "destroy all pipelines and data" - this is irreversible data destruction.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

jm_reset Hidden

jm_reset 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_reset"
  ]
}

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

FAQ

Questions about jm_reset

What does the jm_reset tool do? +

Reset JarvisManager (destroy all pipelines and data). 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_reset? +

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

jm_reset 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_reset? +

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

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

jm_reset 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

team_manager_reset on Team Manager MCP →reset_mcp_runtime_metrics on 0xpdf → All critical-risk MCP tools → The MCP Attack Database →

Guides

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