Medium Risk

add_notebook

PERMISSION REQUIRED — Only when user explicitly asks to add a notebook. Conversation Workflow (Mandatory) When the user says:

How to control add_notebook ↓

AI agents use add_notebook to create or update resources in NotebookLM MCP Structured — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NotebookLM MCP Structured environment.

Medium Risk

add_notebook creates new data (notebook entries) in the user's NotebookLM library. This is reversible (can be deleted via remove_notebook sibling tool), so not Destructive. No code execution, financial transactions, or arbitrary queries involved.

From the tool's definition Tool adds a notebook to a user's library, which creates or modifies data. The description states 'add a notebook', a clear write operation that creates a new resource. Tool name explicitly uses verb 'add'.

Documented attack patterns abuse exactly the kind of access add_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 add_notebook:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_notebook": {
      "limits": [
        {
          "counter": "add_notebook_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

add_notebook stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register NotebookLM MCP Structured — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the add_notebook tool do? +

PERMISSION REQUIRED — Only when user explicitly asks to add a notebook. Conversation Workflow (Mandatory) When the user says:. It is categorised as a Write tool in the NotebookLM MCP Structured MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_notebook? +

Register the NotebookLM MCP Structured 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 MCP Structured. Nothing to install.

What risk level is add_notebook? +

add_notebook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_notebook? +

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.

How do I block add_notebook completely? +

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.

What MCP server provides add_notebook? +

add_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.

Enforce policy on every NotebookLM MCP Structured tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.