search_pages
AI agents call search_pages to retrieve information from Awesome Confluence without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves page search results from Confluence without modifying, deleting, or executing operations. The empty description reduces confidence slightly, but the context of sibling tools (fetch_page_markdown, list_spaces) and the server's stated read-only retrieval focus strongly indicate this is a search/query operation with no side effects.
From the tool's definition Tool named 'search_pages' on a Confluence MCP server described as supporting 'searching...pages'. The server description emphasizes data retrieval operations ('listing, searching, and fetching pages') with no mention of modification or deletion capabilities.
Attacks that exploit this kind of access
search_pages. It is categorised as a Read tool in the Awesome Confluence MCP Server, which means it retrieves data without modifying state.
Register the Awesome Confluence MCP server in PolicyLayer and add a rule for search_pages: 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 Awesome Confluence. Nothing to install.
search_pages 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_pages 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_pages. 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_pages is provided by the Awesome Confluence MCP server (mazhar480/awesome-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 →