List issues where a user has a specific role (assignee, reporter, or creator). Includes date filtering for finding issues within specific time periods.
AI agents call list_issues_by_user_role to retrieve information from Mcp Atlassian 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 issues based on role and time criteria without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal — an agent could over-retrieve data but cannot alter or act upon it. This is a standard Read operation.
From the tool's definition Tool description states 'List issues' and 'finding issues within specific time periods' — purely retrieval operations with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
List issues where a user has a specific role (assignee, reporter, or creator). Includes date filtering for finding issues within specific time periods. It is categorised as a Read tool in the Mcp Atlassian MCP Server, which means it retrieves data without modifying state.
Register the Mcp Atlassian MCP server in PolicyLayer and add a rule for list_issues_by_user_role: 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 Atlassian. Nothing to install.
list_issues_by_user_role 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_issues_by_user_role 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_issues_by_user_role. 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_issues_by_user_role is provided by the Mcp Atlassian MCP server (mcp-atlassian). 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 →