Get details of a specific stage run including all jobs, their states (Scheduled, Building, Completed), results (Passed, Failed), and approval information. Use this to see which jobs failed in a stage, check stage status, or understand the overall stage execution. Essential for identifying which j...
AI agents call get_stage_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 performs read-only retrieval of stage instance metadata and status information from GoCD. It has no side effects on the CI/CD system—it only fetches and displays existing data about pipeline execution states. The blast radius of misuse is minimal (information disclosure only), justifying low severity.
From the tool's definition Tool retrieves stage run details including jobs, states, results, and approval information. The description uses query-focused language: 'Get details', 'see which jobs', 'check stage status', 'understand execution'.
Attacks that exploit this kind of access
Get details of a specific stage run including all jobs, their states (Scheduled, Building, Completed), results (Passed, Failed), and approval information. Use this to see which jobs failed in a stage, check stage status, or understand the overall stage execution. Essential for identifying which job to investigate when a stage fails. 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_stage_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_stage_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_stage_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_stage_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_stage_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 →