Generate a mind map from notebook sources.
AI agents use artifact_generate_mind_map 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.
The tool creates a new artifact (mind map) from existing notebook sources. This is a generative/write operation that produces a new resource. It does not delete data, execute arbitrary code, or involve financial transactions. Severity is medium because misuse could generate unwanted artifacts in a user's notebook, but the blast radius is limited.
From the tool's definition Generate a mind map from notebook sources
Attacks that exploit this kind of access
Generate a mind map from notebook sources. 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 artifact_generate_mind_map: 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.
artifact_generate_mind_map 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 artifact_generate_mind_map 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 artifact_generate_mind_map. 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.
artifact_generate_mind_map 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 →