Get the list of all available Jenkins server names.
AI agents call get_server_names 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 retrieves information about available Jenkins servers—a read-only operation with no side effects, no code execution, and no data modification. The blast radius if misused is minimal; an attacker gains only a list of server names, which does not enable destructive or financial actions by itself. Classification: Read, severity: low.
From the tool's definition Tool name 'get_server_names' and description 'Get the list of all available Jenkins server names' indicate a query operation that retrieves configuration metadata without modifying or executing anything.
Attacks that exploit this kind of access
Get the list of all available Jenkins server names. 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_server_names: 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_server_names 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_server_names 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_server_names. 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_server_names 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 →