Get comprehensive details of a specific pipeline run including build cause (what triggered it), materials (git commits, dependencies), and all stages with their status. Use this to understand why a pipeline ran, what code was built, or see the full pipeline execution details. Essential for invest...
AI agents call get_pipeline_instance to retrieve information from GoCD MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves information about an existing pipeline instance. It does not create, modify, delete, or execute any operations. The description explicitly states it is used to 'understand', 'investigate', and 'see details', all read-only operations. The blast radius of misuse is minimal—an agent could only gain visibility into pipeline execution history and metadata, which is informational only.
From the tool's definition Tool retrieves 'comprehensive details of a specific pipeline run including build cause, materials, and all stages with their status' - pure data retrieval with no modifications, side effects, or state changes.
Attacks that exploit this kind of access
Get comprehensive details of a specific pipeline run including build cause (what triggered it), materials (git commits, dependencies), and all stages with their status. Use this to understand why a pipeline ran, what code was built, or see the full pipeline execution details. Essential for investigating a specific run. It is categorised as a Read tool in the GoCD MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoCD MCP Server MCP server in PolicyLayer and add a rule for get_pipeline_instance: 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 GoCD MCP Server. Nothing to install.
get_pipeline_instance 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 get_pipeline_instance 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 get_pipeline_instance. 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.
get_pipeline_instance is provided by the GoCD MCP Server MCP server (rushi/gocd-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 →