Remove a workflow from a pipeline.
AI agents call remove_workflow_from_pipeline to permanently remove resources in NGS360 MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a workflow from a pipeline destroys that association and could disrupt pipeline execution. While 'add_workflow_to_pipeline' exists as a sibling tool (suggesting reversibility), the act of removal can break ongoing or future pipeline runs and is effectively destructive in nature. The blast radius is high because it could affect sequencing workflows and downstream bioinformatics processes.
From the tool's definition 'Remove a workflow from a pipeline' — removing an association between a workflow and pipeline is likely irreversible without re-adding it manually
Attacks that exploit this kind of access
Remove a workflow from a pipeline. It is categorised as a Destructive tool in the NGS360 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the NGS360 MCP Server MCP server in PolicyLayer and add a rule for remove_workflow_from_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 NGS360 MCP Server. Nothing to install.
remove_workflow_from_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 remove_workflow_from_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 remove_workflow_from_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.
remove_workflow_from_pipeline is provided by the NGS360 MCP Server MCP server (ngs360/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
remove_workflow_from_pipeline is one line of NGS360 MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →