List Jira tickets assigned to you. Quickly see your open, in-progress, or completed tasks. Sorted by last updated.
AI agents call list_my_tickets to retrieve information from Atlassian MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing Jira ticket data assigned to the authenticated user. It has no side effects, creates no new data, executes no operations, and cannot delete or modify tickets. The blast radius of misuse is minimal—an agent could only enumerate the user's tasks, which is already visible in their own Jira account. This is a straightforward read operation.
From the tool's definition Tool name 'list_my_tickets' and description explicitly states it 'List[s] Jira tickets assigned to you' and 'Quickly see your open, in-progress, or completed tasks'. The verb 'list' and 'see' indicate retrieval without modification.
Attacks that exploit this kind of access
List Jira tickets assigned to you. Quickly see your open, in-progress, or completed tasks. Sorted by last updated. It is categorised as a Read tool in the Atlassian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Atlassian MCP Server MCP server in PolicyLayer and add a rule for list_my_tickets: 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 MCP Server. Nothing to install.
list_my_tickets 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 list_my_tickets 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 list_my_tickets. 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.
list_my_tickets is provided by the Atlassian MCP Server MCP server (jaigouk/atlassian-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 →