List generated artifacts in the active NotebookLM notebook.
AI agents call notebooklm_artifact_list 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 list/query operation to retrieve generated artifacts from an existing notebook. It does not create, modify, delete, or execute any operations—it only reads and returns information. The blast radius of misuse is minimal; an AI agent listing artifacts cannot cause harm beyond exposure of existing data within the user's own notebook.
From the tool's definition Tool name 'notebooklm_artifact_list' and description 'List generated artifacts in the active NotebookLM notebook' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List generated artifacts in the active NotebookLM notebook. 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_artifact_list: 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_artifact_list 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_artifact_list 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_artifact_list. 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_artifact_list 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 →