AI agents call list_jobs to retrieve information from Jenkins without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries job metadata from Jenkins without creating, modifying, deleting, or executing any jobs. It is a straightforward read operation that returns information about existing jobs, classified as 'Read' with low severity since listing jobs is informational and has no blast radius if misused by an AI agent.
From the tool's definition Tool name is 'list_jobs' and description states 'List Jenkins jobs' with optional folder scoping. The verb 'list' indicates read-only data retrieval with no modification or execution side effects.
Attacks that exploit this kind of access
List Jenkins jobs. Optionally scoped to a folder path like team/app. It is categorised as a Read tool in the Jenkins MCP Server, which means it retrieves data without modifying state.
Register the Jenkins MCP server in PolicyLayer and add a rule for list_jobs: 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. Nothing to install.
list_jobs 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 list_jobs 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 list_jobs. 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.
list_jobs is provided by the Jenkins MCP server (lokimcpuniverse/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 →