search_in_page
AI agents call search_in_page to retrieve information from 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 searches within Confluence pages, which is a read operation that queries and retrieves data without creating, modifying, or deleting content. The empty description and read-only nature of related tools confirm this is a non-destructive information retrieval function. Severity is low because searches have no side effects and minimal blast radius if invoked by an AI agent.
From the tool's definition Tool name 'search_in_page' with server context 'Confluence MCP Server' that 'Enables reading and analyzing Confluence documentation content' and sibling tools including 'get_confluence_page', 'get_page_attachments', and 'get_page_images' all indicate…
Attacks that exploit this kind of access
search_in_page. It is categorised as a Read tool in the Confluence MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Confluence MCP Server MCP server in PolicyLayer and add a rule for search_in_page: 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 Confluence MCP Server. Nothing to install.
search_in_page 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_in_page 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_in_page. 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_in_page is provided by the Confluence MCP Server MCP server (onclicklistener2048/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 →