AI agents call get_node_config to retrieve information from Jenkins without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration information about Jenkins nodes. While it is a read operation (no side effects), the severity is medium because node configurations may contain sensitive information such as credentials, authentication tokens, environment variables, or details about compute resources that could be exploited if disclosed to an unauthorized actor.
From the tool's definition Tool name 'get_node_config' and description 'Get node config from Jenkins' indicate retrieval of node configuration data with no modification or deletion.
Attacks that exploit this kind of access
Get node config from Jenkins. It is categorised as a Read tool in the Jenkins MCP Server, which means it retrieves data without modifying state.
Register the Jenkins MCP server in PolicyLayer and add a rule for get_node_config: 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. Nothing to install.
get_node_config 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_node_config 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_node_config. 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_node_config is provided by the Jenkins MCP server (mcpland/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 →