cribl_deployPipeline · Cribl MCP: Risk & Policy

WHAT IT DOES

What cribl_deployPipeline does on Cribl

AI agents invoke cribl_deployPipeline to trigger actions in Cribl. 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 cribl_deployPipeline needs a policy

This tool executes a deployment action that activates configurations in a live worker group environment. While not destructive (deployment is reversible via rollback), it is clearly an Execute-category operation because it triggers an external operation whose effects depend on which configuration version and worker group are specified as arguments.

From the tool's definition Tool description states it 'Deploys a specific committed configuration version to a worker group.' Deployment is an active operation that triggers external system effects (configuration activation across infrastructure).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cribl_deployPipeline Rate-limited

cribl_deployPipeline 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": {
    "cribl_deployPipeline": {
      "limits": [
        {
          "counter": "cribl_deploypipeline_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 Cribl, so you can run agents against it safely.

FAQ

Questions about cribl_deployPipeline

What does the cribl_deployPipeline tool do? +

Deploys a specific committed configuration version to a worker group. Returns the list of ConfigGroup objects Cribl provides. It is categorised as a Execute tool in the Cribl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cribl_deployPipeline? +

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

What risk level is cribl_deployPipeline? +

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

Can I rate-limit cribl_deployPipeline? +

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

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

cribl_deployPipeline is provided by the Cribl MCP server (pebbletek/cribl-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.