AI agents use set_node_config to create or update resources in Jenkins — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jenkins environment.
The tool modifies Jenkins node configuration, which is reversible (configs can be changed again) but has significant blast radius—misconfiguration could disrupt CI/CD pipelines, disable build agents, or compromise security settings. It does not delete data (would be Destructive) or execute arbitrary code (would be Execute), making Write the appropriate category.
From the tool's definition Tool name 'set_node_config' and description 'Set specific node config in Jenkins' indicate modification of node configuration settings. This is a write operation that creates or modifies Jenkins infrastructure configuration.
Attacks that exploit this kind of access
Set specific node config in Jenkins. It is categorised as a Write tool in the Jenkins MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jenkins MCP server in PolicyLayer and add a rule for set_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.
set_node_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_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 set_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.
set_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.
set_node_config is one line of Jenkins's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →