Add a local PDF or text/markdown file as a source
AI agents use notebook_add_local_file to create or update resources in Notebooklm — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Notebooklm environment.
The tool writes/creates data by adding a file source to a notebook, which is a reversible modification (sources can be removed). It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because misuse could result in adding malicious or misleading sources to a notebook, potentially tainting analysis results, but the damage is contained to that notebook and reversible.
From the tool's definition 'Add a local PDF or text/markdown file as a source' — this creates a new source entry in a NotebookLM notebook, modifying the notebook's state by ingesting external content.
Documented attack patterns abuse exactly the kind of access notebook_add_local_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Notebooklm, and nothing reaches the server without passing your rules. This is the rule we recommend for notebook_add_local_file:
{
"version": "1",
"default": "deny",
"tools": {
"notebook_add_local_file": {
"limits": [
{
"counter": "notebook_add_local_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}notebook_add_local_file stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a local PDF or text/markdown file as a source. It is categorised as a Write tool in the Notebooklm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Notebooklm MCP server in PolicyLayer and add a rule for notebook_add_local_file: 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.
notebook_add_local_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the notebook_add_local_file 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_add_local_file. 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_add_local_file is provided by the Notebooklm MCP server (moodrobotics/notebooklm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Notebooklm, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Notebooklm tools catalogued and risk-classified — across an index of 43,000+ MCP servers.