notebook_query
AI agents call notebook_query to retrieve information from NotebookLM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Query operations are classified as Read—they retrieve or search data from notebooks without modifying, deleting, or executing external operations. Even without a detailed description, the naming convention and context among primarily generative/write-focused sibling tools suggest this is a retrieval function.
From the tool's definition Tool name 'notebook_query' indicates a query operation against NotebookLM notebooks. The sibling tools show patterns of data creation (audio_overview_create, flashcards_create, infographic_create) and configuration (chat_configure), but notebook_query follows…
Attacks that exploit this kind of access
notebook_query. It is categorised as a Read tool in the NotebookLM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NotebookLM MCP Server MCP server in PolicyLayer and add a rule for notebook_query: 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.
notebook_query 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 notebook_query 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 notebook_query. 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.
notebook_query 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 →