AI agents call delete_block to permanently remove resources in Notion API MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of blocks is a destructive operation that permanently removes data. While the blast radius is limited to individual blocks rather than entire databases, the irreversible nature and potential for cascading content loss in a collaborative workspace (as noted in server description) warrants 'high' severity. Confidence is high because the name and description explicitly indicate deletion without ambiguity.
From the tool's definition Tool name 'delete_block' with description 'Delete blocks' indicates irreversible deletion of content. Notion blocks are fundamental content units; deletion cannot be undone through the API.
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 API 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 blocks. It is categorised as a Destructive tool in the Notion API MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Notion API 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 API 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 API MCP Server MCP server (pbohannon/notion-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Notion API 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 API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.