This record as markdown: /tools/io-github-iowarp-adios-mcp/create-pipeline.md
What create_pipeline does on CLIO Adios
AI agents use create_pipeline 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.
Why create_pipeline is rated Medium
The tool creates a new pipeline environment, which is a reversible write operation. It does not execute user-supplied code or commands (thus not Execute), does not delete data (thus not Destructive), involves no financial transactions (thus not Financial), and has side effects beyond mere data retrieval (thus not Read).
From the tool's definition Tool name is 'create_pipeline' and description states 'Create a new Jarvis-CD pipeline environment,' indicating creation of a new resource/configuration.
Attacks that exploit this kind of access
The rule that runs create_pipeline 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 create_pipeline, this is the rule to start with:
create_pipeline 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.
The button opens the PolicyLayer dashboard: create your workspace, connect CLIO Adios, apply this rule, and every create_pipeline call is checked against it from then on.
Questions about create_pipeline
Create a new Jarvis-CD pipeline environment. 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.
Register the CLIO Adios MCP server in PolicyLayer and add a rule for create_pipeline: 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.
create_pipeline is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_pipeline 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.
Set action: deny in the PolicyLayer policy for create_pipeline. 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.
create_pipeline 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.
More on CLIO Adios, and thousands of servers like it.
This server
Across the catalogue