Notebooklm Codex

9 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated:

3 can modify or destroy data
6 read-only
9 tools total

Community server · catalogue entry verified 02/07/2026

How to control Notebooklm Codex ↓

What Notebooklm Codex exposes to your agents

Read (6) Write / Execute (3) Destructive / Financial (0)
High Risk

The most dangerous Notebooklm Codex tools

3 of Notebooklm Codex's 9 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Notebooklm Codex

PolicyLayer is an MCP gateway — it sits between your AI agents and Notebooklm Codex, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations
{
  "notebooklm_source_add": {
    "limits": [
      {
        "counter": "notebooklm_source_add_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "notebooklm_artifact_list": {
    "limits": [
      {
        "counter": "notebooklm_artifact_list_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Notebooklm Codex — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON NOTEBOOKLM CODEX →

Instant setup, no code required.

All 9 Notebooklm Codex tools

Questions about Notebooklm Codex

How do I prevent bulk modifications through Notebooklm Codex? +

The Notebooklm Codex server has 2 write tools including notebooklm_source_add, notebooklm_use. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Notebooklm Codex.

How many tools does the Notebooklm Codex MCP server expose? +

9 tools across 2 categories: Read, Write. 6 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Notebooklm Codex? +

Register the Notebooklm Codex MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Notebooklm Codex tool call.

Deterministic rules across all 9 Notebooklm Codex tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

9 Notebooklm Codex tools catalogued and risk-classified — across an index of 43,000+ 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.