setup_auth · Notebooklm MCP: Risk & Policy

WHAT IT DOES

What setup_auth does on Notebooklm

AI agents invoke setup_auth to trigger actions in Notebooklm. 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 setup_auth needs a policy

This tool executes a browser action (opens a browser window) to initiate a Google OAuth authentication flow. It triggers an external operation (browser launch and interaction with Google's login system) whose effects depend on the runtime environment. It is not a simple data read or write, but an execution of an external process/browser action.

From the tool's definition Open a browser window for first-time Google login. Returns immediately

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_auth Rate-limited

setup_auth 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": {
    "setup_auth": {
      "limits": [
        {
          "counter": "setup_auth_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, so you can run agents against it safely.

FAQ

Questions about setup_auth

What does the setup_auth tool do? +

Open a browser window for first-time Google login. Returns immediately. It is categorised as a Execute tool in the Notebooklm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on setup_auth? +

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

What risk level is setup_auth? +

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

Can I rate-limit setup_auth? +

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

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

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