search_all
AI agents call search_all 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.
Search tools retrieve and query data without modifying or deleting it. The tool operates in a read-only context alongside other retrieval tools (get_issue, get_issues_bulk, get_comments). No evidence of write, execute, destructive, or financial operations. Confidence is 0.85 rather than higher due to empty description, but the naming convention and server capabilities strongly suggest a standard search query.
From the tool's definition Tool name 'search_all' and server context showing search capabilities for Jira/Confluence; sibling tools include 'get_*' and 'search' operations which are read-only. Description is empty but tool name and context strongly indicate a search/query operation.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
search_all. 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_all: 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_all 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_all 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_all. 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_all is provided by the MCP Atlassian MCP server (omkar9854/mcp-atlassian-onpremdc). 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 →