List installed Jenkins plugins visible through pluginManager/api/json.
AI agents call jenkins_list_plugins to retrieve information from Jenkins Http without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates plugin information from Jenkins without side effects. It is a pure read operation querying the plugin manager API. The information disclosed (list of installed plugins) could inform reconnaissance but does not alter system state. Severity is low as plugin enumeration presents minimal direct risk compared to build execution or job deletion.
From the tool's definition Tool name contains 'list' and description states it 'List installed Jenkins plugins' through a read-only API endpoint (pluginManager/api/json). No modification, deletion, or execution is performed.
Attacks that exploit this kind of access
List installed Jenkins plugins visible through pluginManager/api/json. It is categorised as a Read tool in the Jenkins Http MCP Server, which means it retrieves data without modifying state.
Register the Jenkins Http MCP server in PolicyLayer and add a rule for jenkins_list_plugins: 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 Http. Nothing to install.
jenkins_list_plugins 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_list_plugins 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_list_plugins. 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_list_plugins is provided by the Jenkins Http MCP server (mdtahmidhossain/jenkins-http-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 →