AI agents use cribl_setPipelineConfig to create or update resources in Cribl — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cribl environment.
The tool creates or modifies pipeline configurations in Cribl, affecting system behavior and data processing rules. This is a Write operation (not Execute, as it doesn't directly run arbitrary code; not Destructive, as configurations can be reverted).
From the tool's definition 'Applies a new configuration payload to a specified pipeline' — this modifies pipeline configuration, which is a reversible write operation that changes system state.
Attacks that exploit this kind of access
Applies a new configuration payload to a specified pipeline in a worker group. It is categorised as a Write tool in the Cribl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cribl MCP server in PolicyLayer and add a rule for cribl_setPipelineConfig: 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.
cribl_setPipelineConfig 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 cribl_setPipelineConfig 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 cribl_setPipelineConfig. 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.
cribl_setPipelineConfig 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.
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 →