search_user
AI agents call search_user 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.
The tool name 'search_user' indicates a query or lookup operation to retrieve user data. No description is provided, but the context of an Atlassian server and the naming convention align with read-only operations. The absence of action verbs like 'create', 'update', 'delete', or 'execute' indicates no data modification.
From the tool's definition Tool name 'search_user' combined with sibling tools on the Atlassian MCP server that are predominantly Read operations (get_*, download_*, batch_get_*). The pattern strongly suggests this retrieves user information without side effects.
Attacks that exploit this kind of access
search_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_user: 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_user 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_user 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_user. 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_user is provided by the MCP Atlassian MCP server (sooperset/mcp-atlassian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.