Search Confluence content using CQL (Confluence Query Language). Returns matching pages, blog posts, and other content.
AI agents call confluence_search to retrieve information from Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
confluence_search performs a read-only query operation that retrieves and returns matching content without creating, modifying, or deleting any data. It has no side effects beyond returning search results. The blast radius of misuse is minimal—an agent could retrieve sensitive information it shouldn't access, but cannot modify or destroy data.
From the tool's definition Tool description: 'Search Confluence content using CQL (Confluence Query Language). Returns matching pages, blog posts, and other content.' The verb 'search' and 'returns' indicate data retrieval with no modification or deletion.
Documented attack patterns abuse exactly the kind of access confluence_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Atlassian, and nothing reaches the server without passing your rules. This is the rule we recommend for confluence_search:
{
"version": "1",
"default": "deny",
"tools": {
"confluence_search": {}
}
} confluence_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search Confluence content using CQL (Confluence Query Language). Returns matching pages, blog posts, and other content. It is categorised as a Read tool in the Atlassian MCP Server, which means it retrieves data without modifying state.
Register the Atlassian MCP server in PolicyLayer and add a rule for confluence_search: 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 Atlassian. Nothing to install.
confluence_search 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 confluence_search 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 confluence_search. 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.
confluence_search is provided by the Atlassian MCP server (xuanxt/atlassian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Atlassian, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
51 Atlassian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.