Delete a block in Notion
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 data blocks within Notion. Deletion is the defining characteristic of the Destructive category. While the blast radius is limited to a single block rather than an entire database or workspace, the unrecoverable nature of the operation and potential for accidental/malicious removal of important content justifies high severity.
From the tool's definition Tool name contains 'delete' and description states 'Delete a block in Notion'. The delete operation irreversibly removes data from Notion.
Attacks that exploit this kind of access
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 (tkc/notion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →