delete_page

Delete a page permanently from a workspace. This action is irreversible — the page and its content will be lost. Use get_page first to verify you have the correct page before deleting.

Server Fusebase MCP Server ryan-haver/fusebase-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_page does on Fusebase MCP Server

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

Why delete_page needs a policy

This tool permanently deletes data without recovery options. While it operates on a single page rather than an entire system, the irreversibility and potential loss of user-created content (which may include critical workspace information) makes it destructive. The warning to verify the correct page first acknowledges the severity of the action.

From the tool's definition Tool description states 'Delete a page permanently from a workspace. This action is irreversible — the page and its content will be lost.' The words 'permanently,' 'irreversible,' and 'will be lost' directly indicate destructive capability that cannot be…

Questions about delete_page

What does the delete_page tool do? +

Delete a page permanently from a workspace. This action is irreversible — the page and its content will be lost. Use get_page first to verify you have the correct page before deleting. It is categorised as a Destructive tool in the Fusebase MCP Server 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 delete_page? +

Register the Fusebase MCP Server MCP server in PolicyLayer and add a rule for 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 Fusebase MCP Server. Nothing to install.

What risk level is delete_page? +

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 delete_page? +

Yes. Add a rate_limit block to the 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 delete_page completely? +

Set action: deny in the PolicyLayer policy for 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 delete_page? +

delete_page is provided by the Fusebase MCP Server MCP server (ryan-haver/fusebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.