Search for users by name, email, username, or account ID. Returns display name, email, account status, and account type. Supports pagination.
AI agents call jira_get_users to retrieve information from Mcp Jira Stdio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | — | Search query for user name or email |
startAt | number | — | Index of first result to return |
username | string | — | Specific username to search for |
accountId | string | — | Specific account ID to search for |
maxResults | number | — | Maximum number of results to return |
Parameters from the server's own tool schema.
jira_get_users is a query/search function that retrieves and returns user information without creating, modifying, deleting, or executing any actions. It has no side effects on the Jira system. This is a classic Read operation with minimal security risk—user directory information is typically non-sensitive in enterprise contexts and search-by-design features are standard access controls.
From the tool's definition Tool performs a search operation returning user information (display name, email, account status, account type) with no modification or deletion capability.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Search for users by name, email, username, or account ID. Returns display name, email, account status, and account type. Supports pagination. It is categorised as a Read tool in the Mcp Jira Stdio MCP Server, which means it retrieves data without modifying state.
jira_get_users accepts 5 parameters: query, startAt, username, accountId, maxResults. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Jira Stdio MCP server in PolicyLayer and add a rule for jira_get_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 Mcp Jira Stdio. Nothing to install.
jira_get_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_get_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_get_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_get_users is provided by the Mcp Jira Stdio MCP server (mcp-jira-stdio). 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 →