Get the parameter definitions for a parameterised Jenkins job — names, types, defaults, and choices
AI agents call jenkins_get_job_parameters 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 retrieves static parameter definitions (names, types, defaults, choices) from a Jenkins job without modifying any state, executing builds, or triggering operations. It is a pure read operation with minimal blast radius even if misused by an AI agent.
From the tool's definition Tool name 'jenkins_get_job_parameters' and description 'Get the parameter definitions for a parameterised Jenkins job — names, types, defaults, and choices' indicate retrieval of job configuration metadata with no modification or execution.
Attacks that exploit this kind of access
Get the parameter definitions for a parameterised Jenkins job — names, types, defaults, and choices. 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_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 Mcp Jenkins. Nothing to install.
jenkins_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 jenkins_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 jenkins_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.
jenkins_get_job_parameters 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 →