update_pipeline · NeuronSearchLab MCP: Risk & Policy

WHAT IT DOES

What update_pipeline does on NeuronSearchLab

AI agents use update_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 update_pipeline needs a policy

The tool creates or modifies data reversibly by updating a pipeline configuration. While 'update' is typically a Write operation, the high severity is warranted because modifying a ranking pipeline could significantly impact recommendation quality, user experience, and business outcomes if misconfigured. The damage is reversible (can be reverted/re-updated), preventing classification as Destructive.

From the tool's definition Tool description states 'Update an existing ranking pipeline' - this modifies an existing resource in the recommendation engine system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_pipeline Rate-limited

update_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": {
    "update_pipeline": {
      "limits": [
        {
          "counter": "update_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 update_pipeline

What does the update_pipeline tool do? +

Update an existing ranking pipeline. 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 update_pipeline? +

Register the NeuronSearchLab MCP server in PolicyLayer and add a rule for update_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 update_pipeline? +

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

Can I rate-limit update_pipeline? +

Yes. Add a rate_limit block to the update_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 update_pipeline completely? +

Set action: deny in the PolicyLayer policy for update_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 update_pipeline? +

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