notebooklm_use · Notebooklm Codex MCP: Risk & Policy

WHAT IT DOES

What notebooklm_use does on Notebooklm Codex

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

WHY IT NEEDS A POLICY

Why notebooklm_use needs a policy

This tool changes which notebook is the active context for subsequent operations. While it doesn't create or delete data, it modifies the runtime state of the NotebookLM session. This is a Write-category action because it alters application state in a reversible manner.

From the tool's definition Tool performs 'Set the active NotebookLM notebook context' — this modifies the active state/context, which is a reversible state change to the user's notebook session configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

notebooklm_use Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "notebooklm_use": {
      "limits": [
        {
          "counter": "notebooklm_use_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Notebooklm Codex, so you can run agents against it safely.

FAQ

Questions about notebooklm_use

What does the notebooklm_use tool do? +

Set the active NotebookLM notebook context. It is categorised as a Write tool in the Notebooklm Codex MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on notebooklm_use? +

Register the Notebooklm Codex MCP server in PolicyLayer and add a rule for notebooklm_use: 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 Codex. Nothing to install.

What risk level is notebooklm_use? +

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

Can I rate-limit notebooklm_use? +

Yes. Add a rate_limit block to the notebooklm_use 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 notebooklm_use completely? +

Set action: deny in the PolicyLayer policy for notebooklm_use. 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 notebooklm_use? +

notebooklm_use is provided by the Notebooklm Codex MCP server (knowingdoing/notebooklm-codex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.