Get notebook details with sources.
AI agents call notebook_get 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.
This tool retrieves or queries existing notebook details and associated sources. It has no side effects, does not modify data, and does not execute operations or trigger external changes. It is a straightforward Read operation with minimal security risk - the worst case is unauthorized access to notebook metadata, which has low blast radius.
From the tool's definition Tool name 'notebook_get' and description 'Get notebook details with sources' indicate retrieval of data without modification. The verb 'Get' and the read-only operation of fetching notebook information confirm this is a data retrieval action.
Attacks that exploit this kind of access
Get notebook details with sources. 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_get: 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_get 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_get 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_get. 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_get is provided by the NotebookLM MCP Server MCP server (ran-ai-agency/notebooklm-mcp). 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 →