source_sync_drive · NotebookLM MCP Server MCP: Risk & Policy

WHAT IT DOES

What source_sync_drive does on NotebookLM MCP Server

AI agents use source_sync_drive 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 source_sync_drive needs a policy

This tool modifies notebook state by updating sources with new content from Google Drive. While not destructive (changes are reversible), it is not a read-only operation—it actively updates stored references and content. The confirmation requirement mitigates some risk but does not prevent Write classification.

From the tool's definition Tool name 'source_sync_drive' and description 'Sync Drive sources with latest content' indicates modification of notebook sources by pulling fresh data from Google Drive. The requirement for 'confirm=True' suggests awareness of potential side effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

source_sync_drive Rate-limited

source_sync_drive 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": {
    "source_sync_drive": {
      "limits": [
        {
          "counter": "source_sync_drive_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 source_sync_drive

What does the source_sync_drive tool do? +

Sync Drive sources with latest content. Requires confirm=True. 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 source_sync_drive? +

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

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

Can I rate-limit source_sync_drive? +

Yes. Add a rate_limit block to the source_sync_drive 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 source_sync_drive completely? +

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

source_sync_drive is provided by the NotebookLM MCP Server MCP server (ran-ai-agency/notebooklm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.