Get the parameter definitions of a Jenkins job.
AI agents call get_job_parameters to retrieve information from Jenkins MCP Tool 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 metadata about job parameters without executing jobs, modifying configurations, or triggering builds. It is a pure read operation analogous to fetching job configuration details. The blast radius of misuse is minimal, as an attacker would only gain visibility into parameter definitions, not the ability to execute arbitrary code or modify infrastructure.
From the tool's definition Tool name is 'get_job_parameters' and description states 'Get the parameter definitions of a Jenkins job' — a retrieval operation with no modification or execution of code.
Attacks that exploit this kind of access
Get the parameter definitions of a Jenkins job. It is categorised as a Read tool in the Jenkins MCP Tool MCP Server, which means it retrieves data without modifying state.
Register the Jenkins MCP Tool MCP server in PolicyLayer and add a rule for get_job_parameters: 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 Tool. Nothing to install.
get_job_parameters 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_parameters 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_parameters. 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_parameters is provided by the Jenkins MCP Tool MCP server (xhuaustc/jenkins-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 →