save_auth_tokens · NotebookLM MCP Server MCP: Risk & Policy

WHAT IT DOES

What save_auth_tokens does on NotebookLM MCP Server

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

WHY IT NEEDS A POLICY

Why save_auth_tokens needs a policy

Saving authentication tokens is a Write operation that creates or modifies credential data. Severity is high because misuse could grant persistent unauthorized access to the NotebookLM account and associated resources (notebooks, Drive files, etc.), though it does not directly move money or irreversibly delete data.

From the tool's definition Tool name 'save_auth_tokens' indicates storage of authentication credentials. Empty description limits certainty but the naming strongly suggests credential persistence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_auth_tokens Rate-limited

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

FAQ

Questions about save_auth_tokens

What does the save_auth_tokens tool do? +

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

How do I enforce a policy on save_auth_tokens? +

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

What risk level is save_auth_tokens? +

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

Can I rate-limit save_auth_tokens? +

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

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

save_auth_tokens is provided by the NotebookLM MCP Server MCP server (ran-ai-agency/notebooklm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.