Remove a notebook from the local library. Does NOT delete the
AI agents call remove_notebook to permanently remove resources in Notebooklm — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes/deletes a notebook from the user's library. While the description appears truncated ('Does NOT delete the...'), the primary action is removal of a notebook, which is an irreversible operation. This qualifies as Destructive because notebooks likely contain user-generated notes, references, and data that cannot be recovered once removed.
From the tool's definition Tool name 'remove_notebook' and description 'Remove a notebook from the local library' indicates deletion of a notebook resource. The phrase 'Remove' combined with the context of deleting from a library constitutes irreversible data removal.
Attacks that exploit this kind of access
Remove a notebook from the local library. Does NOT delete the. It is categorised as a Destructive tool in the Notebooklm MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Notebooklm MCP server in PolicyLayer and add a rule for remove_notebook: 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. Nothing to install.
remove_notebook 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 remove_notebook 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 remove_notebook. 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.
remove_notebook is provided by the Notebooklm MCP server (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 →