List every notebook in the local library with its metadata
AI agents call list_notebooks to retrieve information from Notebooklm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries notebook metadata from a local library. It performs only read operations without side effects, making it a Read category risk. Severity is low because listing notebooks poses minimal security risk—it does not modify data, execute code, or expose sensitive operations.
From the tool's definition Tool name 'list_notebooks' combined with description 'List every notebook in the local library with its metadata' indicates pure data retrieval with no modification, deletion, or execution.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every notebook in the local library with its metadata. It is categorised as a Read tool in the Notebooklm MCP Server, which means it retrieves data without modifying state.
Register the Notebooklm MCP server in PolicyLayer and add a rule for list_notebooks: 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. Nothing to install.
list_notebooks 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 list_notebooks 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 list_notebooks. 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.
list_notebooks is provided by the Notebooklm MCP server (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 →