Get one Jenkins view by name.
AI agents call jenkins_get_view 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 Jenkins view information (e.g., a job group or dashboard configuration) by name. It performs a simple GET-style operation that queries data without modifying, deleting, executing code, or affecting financial systems. The blast radius if misused is minimal—an agent could only learn about Jenkins view configurations, not alter infrastructure or trigger builds.
From the tool's definition Tool name 'jenkins_get_view' combined with description 'Get one Jenkins view by name' indicates a retrieval operation with no side effects. The verb 'Get' and the read-only nature of fetching a view configuration aligns with query/fetch semantics.
Attacks that exploit this kind of access
Get one Jenkins view by name. 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_view: 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_view 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_view 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_view. 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_view 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 →