List all Jenkins jobs visible to the configured user.
AI agents call get_jobs 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.
This tool queries and retrieves information (a list of Jenkins jobs) without modifying, executing, or deleting any data. It is a read-only operation that has minimal blast radius if misused by an AI agent—the worst outcome would be information disclosure about available jobs. No reversible or irreversible modifications occur.
From the tool's definition Tool name 'get_jobs' and description 'List all Jenkins jobs' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all Jenkins jobs visible to the configured user. 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 get_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 MCP Server. Nothing to install.
get_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 get_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 get_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.
get_jobs is provided by the Jenkins MCP Server MCP server (mingtian6000/mcpservers). 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 →