AI agents call mind_map_list to retrieve information from Notebooklm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing mind maps without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal security risk, appropriate for an informational/listing capability in a notebook management system.
From the tool's definition Tool name 'mind_map_list' and description 'List all Mind Maps in a notebook' indicate a query/retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access mind_map_list 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 mind_map_list:
{
"version": "1",
"default": "deny",
"tools": {
"mind_map_list": {}
}
}mind_map_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all Mind Maps in a notebook. It is categorised as a Read tool in the Notebooklm MCP Server, which means it retrieves data without modifying state.
Register the Notebooklm MCP server in PolicyLayer and add a rule for mind_map_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. Nothing to install.
mind_map_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 mind_map_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 mind_map_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.
mind_map_list 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.