High Risk →

setup_auth

Google authentication for NotebookLM access - opens a browser window for manual login to your Google account.

How to control setup_auth ↓

AI agents invoke setup_auth to trigger actions in NotebookLM MCP Structured. 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.

High Risk

This tool triggers an external browser action (opening a browser window) to initiate a Google OAuth authentication flow. It performs an external operation whose effects depend on user interaction, placing it in the Execute category. Misuse could expose credentials or hijack authentication sessions, warranting medium severity.

From the tool's definition opens a browser window for manual login to your Google account

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "setup_auth": {
      "limits": [
        {
          "counter": "setup_auth_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

  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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the setup_auth tool do? +

Google authentication for NotebookLM access - opens a browser window for manual login to your Google account. It is categorised as a Execute tool in the NotebookLM MCP Structured 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 Structured 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 MCP Structured. 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 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.