AI agents call jira_get_user_profile to retrieve information from Jiraxmcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user profile information from Jira Cloud without any side effects. It performs a read-only lookup operation, making it a Read category tool. Severity is low because user profile information is typically not sensitive enough to cause significant harm if exposed, though it is subject to normal access controls within Jira.
From the tool's definition Tool name is 'jira_get_user_profile' and description states 'Look up a Jira user profile', indicating a query/retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Look up a Jira user profile. It is categorised as a Read tool in the Jiraxmcp MCP Server, which means it retrieves data without modifying state.
Register the Jirax MCP server in PolicyLayer and add a rule for jira_get_user_profile: 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 Jiraxmcp. Nothing to install.
jira_get_user_profile 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_user_profile 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_user_profile. 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_user_profile is provided by the Jirax MCP server (vaibhavpandeyvpz/jiraxmcp). 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 →