Search for issues based on how a specific user is involved (assignee, reporter, creator, watcher, or any). Provides comprehensive filtering to find all issues a user is connected to.
AI agents call search_issues_by_user_involvement 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 filters existing Jira issues based on user involvement criteria (assignee, reporter, creator, watcher). It performs a query operation with no side effects—it does not create, modify, delete, or execute any actions on the issues or Jira system. The capability to filter and search existing data is characteristic of a Read category tool.
From the tool's definition Tool description states 'Search for issues based on how a specific user is involved' with filtering options. The word 'search' and the focus on retrieval without modification indicates a read-only operation.
Attacks that exploit this kind of access
Search for issues based on how a specific user is involved (assignee, reporter, creator, watcher, or any). Provides comprehensive filtering to find all issues a user is connected to. 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 search_issues_by_user_involvement: 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.
search_issues_by_user_involvement 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 search_issues_by_user_involvement 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 search_issues_by_user_involvement. 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.
search_issues_by_user_involvement 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 →