destroy_pipeline
Destroy a pipeline environment and clean up files.
This record as markdown: /tools/io-github-iowarp-adios-mcp/destroy-pipeline.md
What destroy_pipeline does on CLIO Adios
AI agents call destroy_pipeline 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.
Why destroy_pipeline is rated Critical
The verb 'destroy' combined with 'clean up files' clearly indicates irreversible removal of data and computational environment state. This cannot be undone and has high blast radius if triggered inappropriately by an AI agent (could eliminate entire pipeline setups, computational environments, and associated data files).
From the tool's definition Tool name 'destroy_pipeline' with description 'Destroy a pipeline environment and clean up files' indicates irreversible deletion or removal of data and system resources.
Attacks that exploit this kind of access
The rule that runs destroy_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 destroy_pipeline, this is the rule to start with:
destroy_pipeline is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect CLIO Adios, apply this rule, and every destroy_pipeline call is checked against it from then on.
Questions about destroy_pipeline
Destroy a pipeline environment and clean up files. 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.
Register the CLIO Adios MCP server in PolicyLayer and add a rule for destroy_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.
destroy_pipeline is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the destroy_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 destroy_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.
destroy_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.
Across the catalogue