Get the run history of a pipeline with pagination support. Use this to see recent pipeline runs, find the latest run, check historical results, or identify patterns in failures. Shows run numbers (counters), results, and stage information for each run. Essential for finding a specific pipeline ru...
AI agents call get_pipeline_history 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 retrieves historical pipeline run data for analysis and investigation purposes. It performs a read-only query against the GoCD REST API to fetch and display existing pipeline execution records. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could only retrieve information already available in the system's history logs.
From the tool's definition Tool description states it 'Get[s] the run history of a pipeline' and 'Shows run numbers (counters), results, and stage information for each run.' These are purely informational queries with no side effects.
Attacks that exploit this kind of access
Get the run history of a pipeline with pagination support. Use this to see recent pipeline runs, find the latest run, check historical results, or identify patterns in failures. Shows run numbers (counters), results, and stage information for each run. Essential for finding a specific pipeline run to investigate. 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_history: 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_history 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_history 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_history. 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_history 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 →