Confluence CQL search for content. Builds CQL: text ~ \
AI agents call confluence_search to retrieve information from Jira MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries Confluence content using CQL (Confluence Query Language) without modifying, deleting, or executing arbitrary operations. It is a read-only search capability with no side effects beyond data retrieval. Low severity because search alone has minimal blast radius even if an AI agent misuses the query parameters—it cannot corrupt or delete data.
From the tool's definition Tool description indicates 'Confluence CQL search for content' with text matching via '~' operator. The sibling tools include write/destructive operations (create_page, delete_page, delete_space, add_comment, add_label) but confluence_search itself performs…
Attacks that exploit this kind of access
Confluence CQL search for content. Builds CQL: text ~ \. It is categorised as a Read tool in the Jira MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jira MCP Server 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 Jira MCP Server. 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 Jira MCP Server MCP server (rui-branco/jira-mcp). 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 →