AI agents call pipeline_status to retrieve information from Dobbe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports the status of an existing pipeline without altering its state, triggering execution, or causing any other side effects. It is a pure read operation querying pipeline metadata. Low severity because misuse poses minimal risk—an agent could only gain visibility into pipeline states, not cause operational harm.
From the tool's definition Tool name 'pipeline_status' and description 'Check the current state of a pipeline session' indicate a query operation with no side effects. The verb 'check' is passive; it retrieves state information without modifying or executing anything.
Attacks that exploit this kind of access
Check the current state of a pipeline session. It is categorised as a Read tool in the Dobbe MCP Server, which means it retrieves data without modifying state.
Register the Dobbe MCP server in PolicyLayer and add a rule for pipeline_status: 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.
pipeline_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pipeline_status 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 pipeline_status. 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.
pipeline_status 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.
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 →