notion_delete_block
Delete (archive) a Notion block
This record as markdown: /tools/io-github-alifanov-scopegate/notion-delete-block.md
What notion_delete_block does on ScopeGate
AI agents call notion_delete_block to permanently remove resources in ScopeGate, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why notion_delete_block is rated Critical
The tool performs an irreversible deletion operation on data (a Notion block). Even though described as 'archive,' deletion/archival of user data is a destructive action that cannot be automatically undone and could result in loss of user content if invoked inappropriately by an agent. This is more severe than Write (reversible modification) or Execute (side effects depend on arguments but may not destroy data).
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete (archive) a Notion block' — this irreversibly removes data from a user's Notion workspace.
Attacks that exploit this kind of access
The rule that runs notion_delete_block safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For notion_delete_block, this is the rule to start with:
notion_delete_block is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every notion_delete_block call is checked against it from then on.
Questions about notion_delete_block
Delete (archive) a Notion block. It is categorised as a Destructive tool in the ScopeGate MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ScopeGate 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 ScopeGate. 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 ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
Across the catalogue