Move a page to trash.
AI agents call trash_page 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.
Trashing a page is a destructive action that removes the page (and potentially all its child blocks/content) from active use. Even if Notion has a trash recovery mechanism, the intent and primary effect is deletion, making this Destructive. Misuse by an AI agent could result in loss of important pages and nested content, warranting a high severity rating.
From the tool's definition 'Move a page to trash' — trashing a page removes it from the workspace; while Notion may retain trashed pages temporarily, this is effectively a deletion operation from the user's perspective and is not a simple reversible write.
Attacks that exploit this kind of access
Move a page to trash. 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 trash_page: 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.
trash_page 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 trash_page 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 trash_page. 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.
trash_page is provided by the Notion MCP Server MCP server (lrgex/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 →