confluence_get_page_history

Get version history of a Confluence page

SERVERSage MCP SOURCEsagemcp/sagemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/confluence-get-page-history.md

WHAT IT DOES

What confluence_get_page_history does on Sage MCP

AI agents call confluence_get_page_history to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why confluence_get_page_history is rated Low

This tool retrieves historical version information about a Confluence page. It performs a read-only query operation that does not modify, delete, or execute any code. The worst-case misuse would be unauthorized information disclosure of page edit history, which has low blast radius compared to destructive or financial operations.

From the tool's definition Tool name 'confluence_get_page_history' and description 'Get version history of a Confluence page' indicate retrieval of historical metadata about a page without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs confluence_get_page_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For confluence_get_page_history, this is the rule to start with:

confluence_get_page_history Allowed

confluence_get_page_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "confluence_get_page_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every confluence_get_page_history call is checked against it from then on.

FAQ

Questions about confluence_get_page_history

What does the confluence_get_page_history tool do? +

Get version history of a Confluence page. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on confluence_get_page_history? +

Register the Sage MCP server in PolicyLayer and add a rule for confluence_get_page_history: 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.

What risk level is confluence_get_page_history? +

confluence_get_page_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit confluence_get_page_history? +

Yes. Add a rate_limit block to the confluence_get_page_history 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.

How do I block confluence_get_page_history completely? +

Set action: deny in the PolicyLayer policy for confluence_get_page_history. 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.

What MCP server provides confluence_get_page_history? +

confluence_get_page_history 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.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →