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 operations are irreversible and cannot be undone programmatically. In Notion, blocks represent discrete content units (paragraphs, images, code, tables, etc.). Removing a block destroys that data. This maps to the Destructive category per the rules. The high severity reflects that an AI agent could inadvertently delete important user content.
From the tool's definition Tool name is 'delete-block'. The verb 'delete' combined with 'block' (a fundamental Notion content element) indicates irreversible removal of data. No description provided but the name unambiguously signals deletion.
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-block. 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 (ramidecodes/mcp-server-notion). 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.
17 Notion MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.