Dangerous — requires explicit user confirmation. Confirmation Workflow 1) User requests removal (
AI agents call remove_notebook to permanently remove resources in NotebookLM MCP Structured — 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, which is an irreversible operation that destroys data. Even though it includes a confirmation workflow, the destructive action cannot be undone. Destructive category takes precedence over Write, Execute, and Read categories per the severity hierarchy.
From the tool's definition Tool name 'remove_notebook' combined with description stating 'Dangerous — requires explicit user confirmation' indicates irreversible deletion. The confirmation workflow requirement further confirms destructive intent.
Documented attack patterns abuse exactly the kind of access remove_notebook gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and NotebookLM MCP Structured, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_notebook:
{
"version": "1",
"default": "deny",
"hide": [
"remove_notebook"
]
} remove_notebook 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.
Dangerous — requires explicit user confirmation. Confirmation Workflow 1) User requests removal (. It is categorised as a Destructive tool in the NotebookLM MCP Structured MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the NotebookLM MCP Structured 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 MCP Structured. 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 Structured MCP server (paolodalprato/notebooklm-mcp-structured). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 NotebookLM MCP Structured tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 NotebookLM MCP Structured tools catalogued and risk-classified — across an index of 42,500+ MCP servers.