AI agents call 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.
Deletion of page content is a destructive action that cannot be undone through the tool's normal operation. Although a Notion workspace may have version history or trash recovery, the immediate effect is irreversible removal of data. This is more severe than Write (which creates/modifies reversibly) or Execute (which runs code with context-dependent effects).
From the tool's definition Tool name is 'delete_block' and description states 'Delete a specific block from a page' — the verb 'delete' is explicit and irreversible.
Documented attack patterns abuse exactly the kind of access 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 delete_block:
{
"version": "1",
"default": "deny",
"hide": [
"delete_block"
]
}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 specific block from a page. 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 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.
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 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 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.
delete_block is provided by the Notion MCP Server MCP server (v-3/notion-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Notion MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Notion MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.