Show the active NotebookLM notebook context.
AI agents call notebooklm_status 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 retrieves the status of the active notebook context, which is a read-only operation with no side effects. It falls clearly into the Read category as it queries state information. The severity is low because exposing the current notebook context to an AI agent poses minimal risk—it cannot be exploited to cause harm, financial loss, or data destruction.
From the tool's definition Tool name 'notebooklm_status' and description 'Show the active NotebookLM notebook context' indicate a query operation that retrieves and displays current state information without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Show the active NotebookLM notebook context. 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_status: 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_status 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_status 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_status. 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_status 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 →