Get pipeline stages and their status for a build
AI agents call jenkins_get_pipeline_stages to retrieve information from Mcp Jenkins without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about pipeline stages and their status. It is a read-only operation with no side effects—it does not create, modify, delete, or execute anything. The sibling tools show a pattern of destructive (delete_build, delete_job), write (create_job, copy_job, enable_job), and execute operations (cancel_queue), but this tool is purely informational.
From the tool's definition Tool name 'jenkins_get_pipeline_stages' and description 'Get pipeline stages and their status for a build' use retrieval verbs ('Get'); no modification, deletion, or execution of builds/jobs is performed.
Attacks that exploit this kind of access
Get pipeline stages and their status for a build. It is categorised as a Read tool in the Mcp Jenkins MCP Server, which means it retrieves data without modifying state.
Register the Mcp Jenkins MCP server in PolicyLayer and add a rule for jenkins_get_pipeline_stages: 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 Mcp Jenkins. Nothing to install.
jenkins_get_pipeline_stages 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 jenkins_get_pipeline_stages 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 jenkins_get_pipeline_stages. 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.
jenkins_get_pipeline_stages is provided by the Mcp Jenkins MCP server (@kud/mcp-jenkins). 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 →