Switch to a different Google account or re-authenticate. Use this when: - NotebookLM rate limit is reached (50 queries/day for free accounts) - You want to switch to a different Google account - Authentication is broken and needs a fresh start This will: 1. Close all active browser sessions 2. D...
Bulk/mass operation — affects multiple targets
Part of the Notebooklm MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents may call re_auth to permanently remove or destroy resources in Notebooklm. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call re_auth in a loop, permanently destroying resources in Notebooklm. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
tools:
re_auth:
rules:
- action: deny
reason: "Blocked by default — enable with approval"See the full Notebooklm policy for all 31 tools.
Agents calling destructive-class tools like re_auth have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.
re_auth is one of the critical-risk operations in Notebooklm. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.
Switch to a different Google account or re-authenticate. Use this when: - NotebookLM rate limit is reached (50 queries/day for free accounts) - You want to switch to a different Google account - Authentication is broken and needs a fresh start This will: 1. Close all active browser sessions 2. Delete all saved authentication data (cookies, Chrome profile) 3. Open browser for fresh Google login After completion, use 'get_health' to verify authentication. TROUBLESHOOTING for persistent auth issues: If re_auth fails repeatedly: 1. Ask user to close ALL Chrome/Chromium instances 2. Run cleanup_data(confirm=false, preserve_library=true) to preview old files 3. Run cleanup_data(confirm=true, preserve_library=true) to clean everything except library 4. Run re_auth again for completely fresh start This removes old installation data and browser sessions that can cause conflicts.. It is categorised as a Destructive tool in the Notebooklm MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Add a rule in your Intercept YAML policy under the tools section for re_auth. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Notebooklm MCP server.
re_auth is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the re_auth rule in your Intercept 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 Intercept policy for re_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.
re_auth is provided by the Notebooklm MCP server (@pan-sec/notebooklm-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept