Delete a notebook by ID.
AI agents call notebook_delete to permanently remove resources in NotebookLM MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of a notebook is a destructive action that cannot be undone. It removes user data permanently. While the blast radius is limited to a single notebook (not system-wide), the irreversible nature of deletion and potential loss of research/content justifies the 'Destructive' category and 'high' severity rating. Confidence is high because the intent is unambiguous.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a notebook by ID.' This is an irreversible operation that destroys data.
Attacks that exploit this kind of access
Delete a notebook by ID. It is categorised as a Destructive tool in the NotebookLM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the NotebookLM MCP Server MCP server in PolicyLayer and add a rule for notebook_delete: 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 NotebookLM MCP Server. Nothing to install.
notebook_delete 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 notebook_delete 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 notebook_delete. 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.
notebook_delete is provided by the NotebookLM MCP Server MCP server (pavelguzenfeld/notebooklm-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 →