Add Google Drive document as source.
AI agents use notebook_add_drive to create or update resources in NotebookLM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NotebookLM MCP Server environment.
This tool adds a Google Drive document as a source to a NotebookLM notebook, which modifies the notebook's state and content. This is a Write operation because it creates or updates notebook metadata/structure reversibly without deleting data or executing arbitrary code.
From the tool's definition Tool name 'notebook_add_drive' and description 'Add Google Drive document as source' indicate it creates or modifies notebook content by integrating external sources, which is a reversible write operation.
Attacks that exploit this kind of access
Add Google Drive document as source. It is categorised as a Write tool in the NotebookLM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NotebookLM MCP Server MCP server in PolicyLayer and add a rule for notebook_add_drive: 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.
notebook_add_drive 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 notebook_add_drive 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_add_drive. 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_add_drive 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.
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 →