Get information about a Jenkins job
AI agents call getJob to retrieve information from Jenkins MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
getJob retrieves metadata and configuration information about a Jenkins job without triggering builds, modifying job settings, or causing side effects. It is a simple query operation that extracts existing data. Severity is low because reading job information poses minimal risk—it may reveal configuration details but does not enable destructive, financial, or execution-based attacks without additional tools.
From the tool's definition Tool name 'getJob' and description 'Get information about a Jenkins job' indicate a retrieval operation with no modification or execution.
Attacks that exploit this kind of access
Get information about a Jenkins job. It is categorised as a Read tool in the Jenkins MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jenkins MCP Server MCP server in PolicyLayer and add a rule for getJob: 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 Jenkins MCP Server. Nothing to install.
getJob 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 getJob 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 getJob. 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.
getJob is provided by the Jenkins MCP Server MCP server (umishra1504/jenkins-mcp-server). 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 →