confluence_get_page
Get a Confluence page by id, including its body.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/confluence-get-page.md
What confluence_get_page does on UnClick
AI agents call confluence_get_page 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 |
page_id | string | Yes | Confluence content/page id |
api_token | string | Yes | Atlassian API token |
Parameters from the server's own tool schema.
Why confluence_get_page is rated Low
This tool retrieves page content from Confluence by identifier. It performs a query-like operation that returns data without creating, modifying, deleting, or executing anything. The operation is read-only and poses minimal risk even if called by an AI agent with arbitrary parameters, as it only accesses existing documentation.
From the tool's definition Tool description states 'Get a Confluence page by id, including its body' — the verb 'Get' and the retrieval nature of the operation indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs confluence_get_page 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_get_page, this is the rule to start with:
confluence_get_page 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_get_page call is checked against it from then on.
Questions about confluence_get_page
Get a Confluence page by id, including its body. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
confluence_get_page accepts 4 parameters: site, email, page_id, api_token. Required: site, email, page_id, 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_get_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 UnClick. Nothing to install.
confluence_get_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 confluence_get_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 confluence_get_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.
confluence_get_page 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