List the most recent builds of a pipeline (newest first).
AI agents call list_recent_builds to retrieve information from Netlinq Jenkins without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and returns historical build information without modifying, deleting, or executing anything. It is a straightforward read operation that retrieves metadata about past pipeline executions. Low severity because listing builds poses minimal risk even if misused by an agent—it only exposes build history visibility.
From the tool's definition Tool name is 'list_recent_builds' and description states it 'List the most recent builds of a pipeline (newest first).' This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
List the most recent builds of a pipeline (newest first). It is categorised as a Read tool in the Netlinq Jenkins MCP Server, which means it retrieves data without modifying state.
Register the Netlinq Jenkins MCP server in PolicyLayer and add a rule for list_recent_builds: 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 Netlinq Jenkins. Nothing to install.
list_recent_builds 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 list_recent_builds 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 list_recent_builds. 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.
list_recent_builds is provided by the Netlinq Jenkins MCP server (radhakrishna0018/netlinq-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 →