This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/confluence-search.md
What confluence_search does on UnClick
AI agents call confluence_search to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
site | string | Yes | Atlassian site (e.g. mycompany) |
email | string | Yes | Atlassian account email |
limit | number | — | Results to return (max 50, default 25) |
query | string | Yes | Text to search for |
api_token | string | Yes | Atlassian API token |
Parameters from the server's own tool schema.
Why confluence_search is rated Low
This tool performs a search operation on Confluence documentation, which is a read-only action that retrieves information. It has no capability to create, modify, delete, or execute code. The blast radius of misuse is minimal—an agent could retrieve sensitive or internal documentation, but this is a standard information disclosure risk rather than an active attack vector.
From the tool's definition Tool name 'confluence_search' and description 'Search Confluence pages by text' indicate a query operation that retrieves data without modifying it.
Attacks that exploit this kind of access
The rule that runs confluence_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For confluence_search, this is the rule to start with:
confluence_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every confluence_search call is checked against it from then on.
Questions about confluence_search
Search Confluence pages by text. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
confluence_search accepts 5 parameters: site, email, limit, query, api_token. Required: site, email, query, api_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick 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 UnClick. 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 UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue