Return version history info for a Confluence page.
AI agents call confluence_get_page_history to retrieve information from Mcp Jira Confluence Corp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical metadata about a Confluence page (version changes, timestamps, authors, etc.) without modifying, deleting, or executing any operations. It is a read-only query operation with minimal blast radius—an AI agent misusing it could at worst access potentially sensitive revision information, but cannot alter or destroy data.
From the tool's definition Tool name 'confluence_get_page_history' and description 'Return version history info for a Confluence page' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Return version history info for a Confluence page. It is categorised as a Read tool in the Mcp Jira Confluence Corp MCP Server, which means it retrieves data without modifying state.
Register the Mcp Jira Confluence Corp 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 Mcp Jira Confluence Corp. Nothing to install.
confluence_get_page_history 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_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.
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.
confluence_get_page_history is provided by the Mcp Jira Confluence Corp MCP server (mshegolev/mcp-jira-confluence-corp). 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 →