AI agents call jira_whoami to retrieve information from Mcp Jira without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
jira_whoami retrieves information about the current authenticated user. It has no side effects, performs no data modification, and simply queries user identity metadata. This is a pure read operation with minimal security risk—knowing who is authenticated is information an authorized user would expect to access.
From the tool's definition Tool returns authenticated user info (name, email, accountId) without modifying any data. Description explicitly states 'Return' and notes it is 'Useful for debugging the connection', indicating a read-only operation.
Attacks that exploit this kind of access
Return the authenticated Jira user info (name, email, accountId). Useful for debugging the connection. It is categorised as a Read tool in the Mcp Jira MCP Server, which means it retrieves data without modifying state.
Register the Mcp Jira MCP server in PolicyLayer and add a rule for jira_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 Mcp Jira. Nothing to install.
jira_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 jira_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 jira_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.
jira_whoami is provided by the Mcp Jira MCP server (renan1fps/mcp-jira). 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 →