source_delete

Delete source permanently. IRREVERSIBLE. Requires confirm=True.

Server NotebookLM MCP Server set2374/notebooklm-mcp-archived
Category Destructive
Risk class Critical
Parameters 00 required

What source_delete does on NotebookLM MCP Server

AI agents call source_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 source_delete needs a policy

This tool permanently deletes sources from a NotebookLM notebook without recovery options. While the blast radius is scoped to research sources rather than user accounts or financial systems (preventing 'critical' severity), the irreversible nature of deletion and potential loss of research work justifies 'high' severity and unambiguous 'Destructive' categorization.

From the tool's definition Tool name and description: 'Delete source permanently. IRREVERSIBLE. Requires confirm=True.' The use of 'permanently' and 'IRREVERSIBLE' in all caps, combined with the explicit deletion action, clearly indicates irreversible data destruction.

Questions about source_delete

What does the source_delete tool do? +

Delete source 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 source_delete? +

Register the NotebookLM MCP Server MCP server in PolicyLayer and add a rule for source_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 source_delete? +

source_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 source_delete? +

Yes. Add a rate_limit block to the source_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 source_delete completely? +

Set action: deny in the PolicyLayer policy for source_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 source_delete? +

source_delete is provided by the NotebookLM MCP Server MCP server (set2374/notebooklm-mcp-archived). 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.