Get a Confluence page by ID, including its body content in storage format
AI agents call confluence_get_page to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries Confluence page data by ID without any side effects or mutations. It is a straightforward read operation with minimal blast radius—an agent could retrieve sensitive documentation or private wiki pages if access controls are misconfigured, but cannot modify or delete data. Classified as Read with low severity due to potential information disclosure risks but no destructive capability.
From the tool's definition Tool name 'confluence_get_page' with description 'Get a Confluence page by ID, including its body content in storage format' indicates data retrieval.
Documented attack patterns abuse exactly the kind of access confluence_get_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for confluence_get_page:
{
"version": "1",
"default": "deny",
"tools": {
"confluence_get_page": {}
}
}confluence_get_page is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a Confluence page by ID, including its body content in storage format. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage 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 Sage MCP. 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 Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.