Duplicate an existing pipeline with all its stages and configuration. Useful for creating experiment variants or safe copies before making changes.
AI agents use clone_pipeline to create or update resources in NeuronSearchLab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NeuronSearchLab environment.
Cloning creates a new copy of an existing pipeline. This is a Write operation — it creates new data (the cloned pipeline) but does not destroy the original. The blast radius is medium because it could lead to resource proliferation or unintended pipeline execution if misused, but it is reversible (the clone can be deleted).
From the tool's definition Duplicate an existing pipeline with all its stages and configuration
Attacks that exploit this kind of access
Duplicate an existing pipeline with all its stages and configuration. Useful for creating experiment variants or safe copies before making changes. It is categorised as a Write tool in the NeuronSearchLab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NeuronSearchLab MCP server in PolicyLayer and add a rule for clone_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 NeuronSearchLab. Nothing to install.
clone_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 clone_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 clone_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.
clone_pipeline is provided by the NeuronSearchLab MCP server (neuronsearchlab/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →