Delete a Confluence page
AI agents call confluence_delete_page to permanently remove resources in Jira & Confluence MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of a page is an irreversible operation that cannot be undone through normal means. This falls squarely into the Destructive category per the classification rules. While not catastrophic organization-wide (hence 'high' rather than 'critical'), unauthorized deletion of documentation pages could cause significant operational disruption and knowledge loss.
From the tool's definition Tool name 'confluence_delete_page' and description 'Delete a Confluence page' explicitly indicate irreversible deletion of data.
Attacks that exploit this kind of access
Delete a Confluence page. It is categorised as a Destructive tool in the Jira & Confluence MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jira & Confluence MCP Server MCP server in PolicyLayer and add a rule for confluence_delete_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 Jira & Confluence MCP Server. Nothing to install.
confluence_delete_page is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the confluence_delete_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_delete_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_delete_page is provided by the Jira & Confluence MCP Server MCP server (katsuhirohonda/jira-confluence-mcp). 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 →