notebook_rename · NotebookLM MCP Server MCP: Risk & Policy

WHAT IT DOES

What notebook_rename does on NotebookLM MCP Server

AI agents use notebook_rename 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.

WHY IT NEEDS A POLICY

Why notebook_rename needs a policy

Renaming a notebook is a reversible write operation that modifies notebook properties but does not delete data or trigger external code execution. The change can be undone by renaming again, placing it in the Write category rather than Destructive.

From the tool's definition Tool name 'notebook_rename' and description 'Rename a notebook' indicate modification of existing notebook metadata without deletion or irreversible changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

notebook_rename Rate-limited

notebook_rename 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "notebook_rename": {
      "limits": [
        {
          "counter": "notebook_rename_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches NotebookLM MCP Server, so you can run agents against it safely.

FAQ

Questions about notebook_rename

What does the notebook_rename tool do? +

Rename a notebook. 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.

How do I enforce a policy on notebook_rename? +

Register the NotebookLM MCP Server MCP server in PolicyLayer and add a rule for notebook_rename: 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.

What risk level is notebook_rename? +

notebook_rename is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit notebook_rename? +

Yes. Add a rate_limit block to the notebook_rename 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.

How do I block notebook_rename completely? +

Set action: deny in the PolicyLayer policy for notebook_rename. 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.

What MCP server provides notebook_rename? +

notebook_rename 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.