Search for Confluence content using CQL
AI agents call confluence_search_content to retrieve information from Jira & Confluence 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 data from Confluence using CQL (Confluence Query Language) without creating, modifying, or deleting any content. It is purely informational and has no side effects beyond returning search results. The blast radius of misuse is minimal—worst case an agent performs unwanted searches, exposing information it already has access to read.
From the tool's definition Tool name 'confluence_search_content' and description 'Search for Confluence content using CQL' indicate a query/search operation with no modification or deletion capability.
Attacks that exploit this kind of access
Search for Confluence content using CQL. It is categorised as a Read tool in the Jira & Confluence MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jira & Confluence MCP Server MCP server in PolicyLayer and add a rule for confluence_search_content: 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 & Confluence MCP Server. Nothing to install.
confluence_search_content 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_content 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_content. 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_content is provided by the Jira & Confluence MCP Server MCP server (katsuhirohonda/jira-confluence-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 →