deactivate_pipeline · NeuronSearchLab MCP: Risk & Policy

WHAT IT DOES

What deactivate_pipeline does on NeuronSearchLab

AI agents use deactivate_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.

WHY IT NEEDS A POLICY

Why deactivate_pipeline needs a policy

Deactivating a pipeline stops it from serving results, which is a reversible state change (it can be reactivated) — making it Write rather than Destructive. However, the blast radius is high because disabling a ranking pipeline would immediately halt recommendation delivery for all users relying on it, potentially disrupting the entire service.

From the tool's definition Deactivate a ranking pipeline so it stops serving results without being deleted

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deactivate_pipeline Rate-limited

deactivate_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deactivate_pipeline": {
      "limits": [
        {
          "counter": "deactivate_pipeline_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches NeuronSearchLab, so you can run agents against it safely.

FAQ

Questions about deactivate_pipeline

What does the deactivate_pipeline tool do? +

Deactivate a ranking pipeline so it stops serving results without being deleted. 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.

How do I enforce a policy on deactivate_pipeline? +

Register the NeuronSearchLab MCP server in PolicyLayer and add a rule for deactivate_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.

What risk level is deactivate_pipeline? +

deactivate_pipeline is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit deactivate_pipeline? +

Yes. Add a rate_limit block to the deactivate_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.

How do I block deactivate_pipeline completely? +

Set action: deny in the PolicyLayer policy for deactivate_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.

What MCP server provides deactivate_pipeline? +

deactivate_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.