Get information about the currently authenticated user
AI agents call jira_get_current_user to retrieve information from Jira MCP Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple data retrieval operation to fetch metadata about the current user. It does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal—an attacker would only gain knowledge of user identity/attributes already accessible in the authentication context. No data integrity, financial, or system execution risks exist.
From the tool's definition Tool name and description indicate retrieval of user information: 'Get information about the currently authenticated user'. This is a read-only operation with no side effects.
Attacks that exploit this kind of access
Get information about the currently authenticated user. It is categorised as a Read tool in the Jira MCP Integration MCP Server, which means it retrieves data without modifying state.
Register the Jira MCP Integration MCP server in PolicyLayer and add a rule for jira_get_current_user: 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 Jira MCP Integration. Nothing to install.
jira_get_current_user 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_get_current_user 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_get_current_user. 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_get_current_user is provided by the Jira MCP Integration MCP server (koveh/jira-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 →