Critical Risk →

confluence_delete_page

Delete a Confluence page by ID

How to control confluence_delete_page ↓

AI agents call confluence_delete_page to permanently remove resources in Sage MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Deleting a Confluence page is a destructive action that permanently removes content and cannot be undone. This fits the Destructive category (irreversibly deletes data). Severity is high because accidental or malicious deletion of documentation pages can disrupt team workflows and cause data loss, though the impact is typically scoped to that specific page rather than system-wide infrastructure.

From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete a Confluence page by ID' — this is an irreversible deletion operation.

Documented attack patterns abuse exactly the kind of access confluence_delete_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_delete_page:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "confluence_delete_page"
  ]
}

confluence_delete_page disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the confluence_delete_page tool do? +

Delete a Confluence page by ID. It is categorised as a Destructive tool in the Sage MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on confluence_delete_page? +

Register the Sage 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 Sage MCP. Nothing to install.

What risk level is confluence_delete_page? +

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.

Can I rate-limit confluence_delete_page? +

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.

How do I block confluence_delete_page completely? +

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.

What MCP server provides confluence_delete_page? +

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

Enforce policy on every Sage MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.