Import discovered sources into notebook.
AI agents use research_import to create or update resources in NotebookLM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NotebookLM MCP Server environment.
This tool creates or modifies data (notebook contents) in a reversible manner. Users can remove imported sources later, making it a Write operation rather than Destructive. The severity is medium because importing unvetted or malicious sources could contaminate a research notebook, but the action itself is not irreversible and the blast radius is limited to the affected notebook.
From the tool's definition The tool 'research_import' imports sources into a notebook, which modifies the notebook's contents by adding new sources. The verb 'import' indicates data creation/addition rather than mere retrieval.
Attacks that exploit this kind of access
Import discovered sources into notebook. It is categorised as a Write tool in the NotebookLM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NotebookLM MCP Server MCP server in PolicyLayer and add a rule for research_import: 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.
research_import 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 research_import 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 research_import. 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.
research_import 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 →