AI agents call notion_delete_block to permanently remove resources in Notion MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible deletion of Notion blocks, which is a destructive operation that cannot be undone by the tool itself. While not as critical as deleting entire databases or workspaces, the loss of block content is permanent and could impact important documents.
From the tool's definition Tool name 'notion_delete_block' and description 'Delete a block in Notion' explicitly indicate irreversible deletion of data. Deletion operations cannot be undone without manual recovery or backups.
Documented attack patterns abuse exactly the kind of access notion_delete_block gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Notion MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for notion_delete_block:
{
"version": "1",
"default": "deny",
"hide": [
"notion_delete_block"
]
} notion_delete_block disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a block in Notion. It is categorised as a Destructive tool in the Notion MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Notion MCP Server MCP server in PolicyLayer and add a rule for notion_delete_block: 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 Notion MCP Server. Nothing to install.
notion_delete_block 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 notion_delete_block 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 notion_delete_block. 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.
notion_delete_block is provided by the Notion MCP Server MCP server (orbit-logistics/notion-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Notion MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Notion MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.