AI agents use slide_deck_create 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.
This tool creates and generates a new slide deck resource based on existing notebook sources. This is a Write operation because it produces new data/content that is stored in the system and can be modified or deleted later. It is not Destructive (reversible), not Execute (doesn't run arbitrary code), and not Financial.
From the tool's definition Tool name 'slide_deck_create' and description 'Generate a slide deck from notebook sources' indicate creation of new content artifact within the NotebookLM system.
Documented attack patterns abuse exactly the kind of access slide_deck_create 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 slide_deck_create:
{
"version": "1",
"default": "deny",
"tools": {
"slide_deck_create": {
"limits": [
{
"counter": "slide_deck_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}slide_deck_create 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.
Generate a slide deck from notebook sources. 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 slide_deck_create: 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.
slide_deck_create 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 slide_deck_create 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 slide_deck_create. 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.
slide_deck_create 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.