AI agents use report_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 new data (a written report) based on existing notebook sources. The action is reversible (reports can be deleted or regenerated), making it a Write operation rather than Execute or Destructive. Severity is medium because while report generation is generally safe, it could be misused to create misleading or false documents if the agent manipulates source context.
From the tool's definition Tool name is 'report_create' and description states 'Generate a written report from notebook sources', indicating creation of new content.
Documented attack patterns abuse exactly the kind of access report_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 report_create:
{
"version": "1",
"default": "deny",
"tools": {
"report_create": {
"limits": [
{
"counter": "report_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}report_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 written report 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 report_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.
report_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 report_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 report_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.
report_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.