Check whether the local NotebookLM CLI is authenticated.
AI agents call notebooklm_auth_check to retrieve information from Notebooklm Codex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only check of authentication state. It retrieves information (whether authentication is valid) with no side effects, data modifications, or external operations triggered. The blast radius of misuse is minimal — an agent could only learn the authentication status, which does not compromise data or trigger unwanted actions.
From the tool's definition Tool name is 'notebooklm_auth_check' and description states it 'Check[s] whether the local NotebookLM CLI is authenticated' — a query operation that retrieves authentication status without modifying anything.
Attacks that exploit this kind of access
Check whether the local NotebookLM CLI is authenticated. It is categorised as a Read tool in the Notebooklm Codex MCP Server, which means it retrieves data without modifying state.
Register the Notebooklm Codex MCP server in PolicyLayer and add a rule for notebooklm_auth_check: 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 Codex. Nothing to install.
notebooklm_auth_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the notebooklm_auth_check 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 notebooklm_auth_check. 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.
notebooklm_auth_check is provided by the Notebooklm Codex MCP server (knowingdoing/notebooklm-codex). 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 →