Search for Jira users by name or email. Returns account IDs and display names. Use this to find users for mentions or assignments. When multiple Jira instances are configured, use the
AI agents call jira_search_users to retrieve information from Jira MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only searches and retrieves user information from Jira. It has no side effects—it does not create, modify, delete, or execute any operations. The severity is low because user directory information is generally not sensitive in most organizational contexts, and the blast radius of misuse (e.g., discovering user IDs) is minimal compared to other risk categories.
From the tool's definition Tool description states 'Search for Jira users by name or email. Returns account IDs and display names.' This is a search/query operation that retrieves user data without modifying anything.
Attacks that exploit this kind of access
Search for Jira users by name or email. Returns account IDs and display names. Use this to find users for mentions or assignments. When multiple Jira instances are configured, use the. It is categorised as a Read tool in the Jira MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jira MCP Server MCP server in PolicyLayer and add a rule for jira_search_users: 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 Server. Nothing to install.
jira_search_users 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_search_users 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_search_users. 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_search_users is provided by the Jira MCP Server MCP server (rui-branco/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 →