Get details for a specific Jira user by username, account ID, or email. Returns user profile information.
AI agents call get_jira_user to retrieve information from Mcp Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query that returns existing user profile data with no side effects. It does not create, modify, delete, or execute operations. While user information can be considered sensitive, the low blast radius and reversible nature of data retrieval places it in the Read category with low severity.
From the tool's definition Tool retrieves user profile information ('Returns user profile information') without modifying or deleting data. Parameters are lookup identifiers (username, account ID, email) indicating a query operation.
Attacks that exploit this kind of access
Get details for a specific Jira user by username, account ID, or email. Returns user profile information. It is categorised as a Read tool in the Mcp Atlassian MCP Server, which means it retrieves data without modifying state.
Register the Mcp Atlassian MCP server in PolicyLayer and add a rule for get_jira_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 Mcp Atlassian. Nothing to install.
get_jira_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 get_jira_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 get_jira_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.
get_jira_user is provided by the Mcp Atlassian MCP server (mcp-atlassian). 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 →