Get the execution history of a specific job across multiple pipeline runs. Use this to see historical trends, past runs, or to find a specific job instance.
AI agents call get_job_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 execution data from GoCD without modifying, executing, or deleting any pipelines, jobs, or artifacts. It is a pure read operation that queries build history metadata. There is minimal risk from misuse—an AI could at worst retrieve historical information it shouldn't see, but cannot trigger builds, cancel operations, delete data, or affect system state.
From the tool's definition Tool name 'get_job_history' and description 'Get the execution history of a specific job across multiple pipeline runs' clearly indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Get the execution history of a specific job across multiple pipeline runs. Use this to see historical trends, past runs, or to find a specific job instance. 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_job_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_job_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_job_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_job_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_job_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 →