Get the complete console log output for a specific job run. Use this to see build logs, compilation errors, runtime errors, stack traces, or any output written to stdout/stderr during job execution. Essential for debugging build failures and understanding what happened during execution.
AI agents call get_job_console 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 retrieves and displays historical log data from a completed or running job. It does not modify, execute, trigger, or delete anything. The severity is low because console logs typically contain non-sensitive build metadata, though in some environments logs might contain credentials or sensitive information—however, the tool itself performs no destructive action.
From the tool's definition Tool name 'get_job_console' and description explicitly states it 'Get[s] the complete console log output' for a job run. It retrieves build logs, compilation errors, and execution output—read-only operations with no side effects.
Attacks that exploit this kind of access
Get the complete console log output for a specific job run. Use this to see build logs, compilation errors, runtime errors, stack traces, or any output written to stdout/stderr during job execution. Essential for debugging build failures and understanding what happened during execution. 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_console: 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_console 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_console 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_console. 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_console 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 →