Return the authenticated Jenkins identity from /whoAmI/api/json.
AI agents call jenkins_whoami 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 queries the Jenkins /whoAmI/api/json endpoint to retrieve the current authenticated user's identity. It performs no modifications, deletions, or side effects—it simply reads and returns authentication identity data. This is a basic information retrieval operation with minimal blast radius if misused (disclosure of current user identity only).
From the tool's definition Tool name 'jenkins_whoami' and description 'Return the authenticated Jenkins identity from /whoAmI/api/json' indicates a query operation that retrieves identity information without modification.
Attacks that exploit this kind of access
Return the authenticated Jenkins identity from /whoAmI/api/json. 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_whoami: 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_whoami 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_whoami 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_whoami. 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_whoami 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 →