Register a NotebookLM notebook in the local library so it can be
AI agents use add_notebook to create or update resources in Notebooklm — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Notebooklm environment.
This tool creates a new notebook entry in a local library, which is a reversible write operation. It does not retrieve data (Read), execute arbitrary code (Execute), delete data (Destructive), or move money (Financial). The impact is limited to adding metadata about a notebook to a local registry, making it a low-severity Write action.
From the tool's definition Tool name is 'add_notebook' and description states 'Register a NotebookLM notebook in the local library so it can be'. The word 'Register' and 'add' indicate data creation/modification in a local library structure.
Attacks that exploit this kind of access
Register a NotebookLM notebook in the local library so it can be. It is categorised as a Write tool in the Notebooklm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Notebooklm MCP server in PolicyLayer and add a rule for add_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.
add_notebook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_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 →