List artifacts exported on a build JSON API response.
AI agents call jenkins_get_build_artifacts 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 lists build artifacts from Jenkins, which is a read operation with no side effects. The artifacts already exist and the tool merely enumerates them. The blast radius of misuse is minimal - an attacker gains visibility into build outputs but cannot modify, delete, or execute anything. Confidence is high because the intent is unambiguous from both name and description.
From the tool's definition Tool name contains 'get' and description states 'List artifacts' - both indicate read-only retrieval. No modification, execution, or deletion operations are described.
Attacks that exploit this kind of access
List artifacts exported on a build JSON API response. 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_get_build_artifacts: 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_get_build_artifacts 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_get_build_artifacts 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_get_build_artifacts. 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_get_build_artifacts 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 →