notebooklm_generate_audio · Notebooklm Codex MCP

WHAT IT DOES

What notebooklm_generate_audio does on Notebooklm Codex

AI agents invoke notebooklm_generate_audio to trigger actions in Notebooklm Codex. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why notebooklm_generate_audio needs a policy

This tool triggers an external generation operation (audio synthesis) in NotebookLM. It doesn't merely read data nor does it irreversibly delete anything, but it initiates a compute/generation process with external side effects (creating an audio artifact). This maps best to Execute, as it triggers an external operation whose output depends on the current notebook's contents.

From the tool's definition "Generate an audio overview for the active NotebookLM notebook"

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

notebooklm_generate_audio Rate-limited

notebooklm_generate_audio stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_generate_audio": {
      "limits": [
        {
          "counter": "notebooklm_generate_audio_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_generate_audio

What does the notebooklm_generate_audio tool do? +

Generate an audio overview for the active NotebookLM notebook. It is categorised as a Execute tool in the Notebooklm Codex MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on notebooklm_generate_audio? +

Register the Notebooklm Codex MCP server in PolicyLayer and add a rule for notebooklm_generate_audio: 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_generate_audio? +

notebooklm_generate_audio is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit notebooklm_generate_audio? +

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

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

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