notebook_delete

Delete notebook permanently. IRREVERSIBLE. Requires confirm=True.

Server NotebookLM MCP Server ran-ai-agency/notebooklm-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What notebook_delete does on NotebookLM MCP Server

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.

Why notebook_delete needs a policy

This tool permanently deletes notebooks without recovery options, which is the defining characteristic of the Destructive category. The confirmation flag requirement does not reduce the severity since an agent could bypass it programmatically. The blast radius is high because an agent could delete all user notebooks or research work, though not financial in nature, hence high rather than critical severity.

From the tool's definition Tool description explicitly states 'Delete notebook permanently' and 'IRREVERSIBLE' with a confirmation requirement, indicating this tool irreversibly removes data without undo capability.

Questions about notebook_delete

What does the notebook_delete tool do? +

Delete notebook permanently. IRREVERSIBLE. Requires confirm=True. 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.

How do I enforce a policy on notebook_delete? +

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.

What risk level is notebook_delete? +

notebook_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit notebook_delete? +

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.

How do I block notebook_delete completely? +

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.

What MCP server provides notebook_delete? +

notebook_delete is provided by the NotebookLM MCP Server MCP server (ran-ai-agency/notebooklm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.