jm_list_pipelines

List all existing Jarvis pipelines.

SERVERCLIO Adios SOURCEpypi:clio-kit

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What jm_list_pipelines does on CLIO Adios

AI agents call jm_list_pipelines to retrieve information from CLIO Adios without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why jm_list_pipelines is rated Low

This tool retrieves and displays information about existing pipelines without creating, modifying, deleting, or executing any operations. It is a simple read operation that enumerates available resources, posing minimal security risk.

From the tool's definition Tool name 'jm_list_pipelines' and description 'List all existing Jarvis pipelines' indicate a query/retrieval operation with no data modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

jm_list_pipelines Allowed

jm_list_pipelines is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jm_list_pipelines": {}
  }
}

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

FAQ

Questions about jm_list_pipelines

What does the jm_list_pipelines tool do? +

List all existing Jarvis pipelines. It is categorised as a Read tool in the CLIO Adios MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on jm_list_pipelines? +

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

jm_list_pipelines is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit jm_list_pipelines? +

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

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

jm_list_pipelines 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →