pipeline_start · Dobbe MCP: Risk & Policy

WHAT IT DOES

What pipeline_start does on Dobbe

AI agents invoke pipeline_start to trigger actions in Dobbe. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why pipeline_start needs a policy

This tool initiates execution of DevOps automation workflows. While it does not directly delete data (not Destructive) or move money (not Financial), it starts processes that execute code, run tests, and perform code reviews—operations that have side effects dependent on arguments and pipeline state.

From the tool's definition Tool description states 'Start a new dobbe pipeline' which initiates automated DevOps workflows. Server description confirms these workflows include 'vulnerability resolution, code review, test generation' and use 'a state machine for reliable execution.'…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pipeline_start Rate-limited

pipeline_start stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pipeline_start": {
      "limits": [
        {
          "counter": "pipeline_start_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about pipeline_start

What does the pipeline_start tool do? +

Start a new dobbe pipeline. Returns the first step instruction for Claude to follow. It is categorised as a Execute tool in the Dobbe MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pipeline_start? +

Register the Dobbe MCP server in PolicyLayer and add a rule for pipeline_start: 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 Dobbe. Nothing to install.

What risk level is pipeline_start? +

pipeline_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pipeline_start? +

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

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

pipeline_start is provided by the Dobbe MCP server (nareshnavinash/dobbe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.