get_user_tickets
AI agents call get_user_tickets 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.
The tool retrieves user tickets from Jira without modifying, deleting, or executing operations. This is a read-only query operation with minimal blast radius if misused—an AI agent could retrieve ticket information but cannot alter state or cause harm. Low severity reflects the informational nature of the action.
From the tool's definition Tool name 'get_user_tickets' implies retrieval of ticket data. No description provided, but context from sibling tools (comment_on_ticket, create_ticket, update_ticket_status) and server description stating 'fetching tickets' as a core operation confirms this…
Attacks that exploit this kind of access
get_user_tickets. 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 get_user_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 Jira MCP Server. Nothing to install.
get_user_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 get_user_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 get_user_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.
get_user_tickets is provided by the Jira MCP Server MCP server (maximepeabody/simple-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 →