Search pages based on a user
AI agents call search_pages_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 queries or filters pages by user involvement criteria. It retrieves information without creating, modifying, deleting, or executing anything. The operation has no side effects and poses minimal risk even if misused by an AI agent—the worst outcome would be retrieval of information the agent is already authorized to access.
From the tool's definition Tool name 'search_pages_by_user_involvement' and description 'Search pages based on a user' indicate a query/search operation that retrieves data without modification. The word 'search' is a classic Read operation.
Attacks that exploit this kind of access
Search pages based on a user. 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_pages_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_pages_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_pages_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_pages_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_pages_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 →