AI agents call notebook_delete 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 permanently deletes a notebook and its contents with no undo capability. Permanent data deletion is categorized as Destructive. Severity is high because an AI agent misusing this tool could irreversibly destroy user research work and data, though the impact is scoped to a single notebook rather than system-wide (which would be critical).
From the tool's definition Tool description explicitly states: 'Delete a notebook permanently. IRREVERSIBLE.' The use of 'DELETE' in the tool name combined with 'permanently' and all-caps 'IRREVERSIBLE' confirms this is an irreversible data deletion operation.
Documented attack patterns abuse exactly the kind of access notebook_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Notebooklm, and nothing reaches the server without passing your rules. This is the rule we recommend for notebook_delete:
{
"version": "1",
"default": "deny",
"hide": [
"notebook_delete"
]
}notebook_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a notebook permanently. IRREVERSIBLE. 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 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. 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 (moodrobotics/notebooklm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Notebooklm, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Notebooklm tools catalogued and risk-classified — across an index of 43,000+ MCP servers.