Retrieves issues assigned to current user, sorted by most recently updated first. Supports pagination and field selection. For pagination, use nextPageToken from previous response.
AI agents call jira_get_my_issues 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 |
|---|---|---|---|
expand | array | — | Additional details to include |
fields | array | — | Specific fields to retrieve |
maxResults | number | — | Maximum number of results to return per page |
nextPageToken | string | — | Token for pagination. Omit for first page, use value from previous response for next page. |
Parameters from the server's own tool schema.
This tool performs a read-only query operation that retrieves and filters existing Jira issues. It supports pagination and field selection but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal — an agent could only retrieve issues already assigned to the authenticated user, posing no financial, destructive, or execution risk.
From the tool's definition Tool name contains 'get' and description states 'Retrieves issues assigned to current user' with 'pagination and field selection' — purely data retrieval with no mutation or side effects.
Attacks that exploit this kind of access
Retrieves issues assigned to current user, sorted by most recently updated first. Supports pagination and field selection. For pagination, use nextPageToken from previous response. It is categorised as a Read tool in the Mcp Jira Stdio MCP Server, which means it retrieves data without modifying state.
jira_get_my_issues accepts 4 parameters: expand, fields, maxResults, nextPageToken. 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_my_issues: 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_my_issues 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_my_issues 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_my_issues. 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_my_issues 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 →