Search for Jira user accounts by name or email
AI agents call lookupJiraAccountId to retrieve information from Atlassian Multi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves account information (user IDs) based on search criteria. It has no capability to modify, delete, or execute operations—it simply queries and returns existing data. This is a straightforward read operation with minimal risk; the worst case is unauthorized discovery of account IDs, which are typically non-sensitive identifiers in Jira systems.
From the tool's definition Tool performs a 'Search' operation for user accounts by name or email, with no modification or deletion capability indicated. The description explicitly states it queries/looks up data without side effects.
Attacks that exploit this kind of access
Search for Jira user accounts by name or email. It is categorised as a Read tool in the Atlassian Multi MCP Server, which means it retrieves data without modifying state.
Register the Atlassian Multi MCP server in PolicyLayer and add a rule for lookupJiraAccountId: 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 Atlassian Multi. Nothing to install.
lookupJiraAccountId 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 lookupJiraAccountId 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 lookupJiraAccountId. 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.
lookupJiraAccountId is provided by the Atlassian Multi MCP server (ntlongctt/atlassian-multi-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 →