save_auth_tokens
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.
Saving auth tokens is a write operation that creates or modifies credential data. While not destructive (tokens can be replaced), it is severe because misuse could persist unauthorized access credentials, compromising the NotebookLM account.
From the tool's definition Tool name 'save_auth_tokens' indicates persistent storage of authentication credentials. The description is empty, limiting direct evidence, but the function name clearly implies writing/storing sensitive authentication material.
Attacks that exploit this kind of access
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.
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.
save_auth_tokens is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
save_auth_tokens is provided by the NotebookLM MCP Server MCP server (set2374/notebooklm-mcp-archived). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →