Get details of a specific source.
AI agents call source_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 metadata or details about a source in NotebookLM. It performs a query operation that returns data without creating, modifying, deleting, or executing any actions. The verb 'get' is characteristic of Read operations. No data modification, deletion, or external execution occurs. The low severity reflects minimal blast radius if misused—an agent would only retrieve details it is authorized to view.
From the tool's definition Tool name 'source_get' and description 'Get details of a specific source' indicate retrieval of information without modification or side effects.
Attacks that exploit this kind of access
Get details of a specific source. 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 source_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.
source_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 source_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 source_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.
source_get is provided by the NotebookLM MCP Server MCP server (pavelguzenfeld/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 →