// MCP TOOL REFERENCE

cleanup_data

ULTRATHINK Deep Cleanup - Scans entire system for ALL NotebookLM MCP data files across 8 categories. Always runs in deep mode, shows categorized preview before deletion.\n\n

ServerNotebookLM MCP Structured
CategoryDestructive

How to control cleanup_data ↓

WHAT CLEANUP_DATA ON NOTEBOOKLM MCP STRUCTURED DOES

AI agents call cleanup_data to permanently remove resources in NotebookLM MCP Structured — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

THE RISK

Critical Risk

This tool explicitly deletes data files across 8 categories system-wide. The word 'deletion' and 'cleanup' indicate irreversible destruction of data. The blast radius is critical because it operates on the 'entire system' across ALL data files, meaning misuse could wipe all NotebookLM MCP data irreversibly.

From the tool's definition 'cleanup_data' with description 'Deep Cleanup - Scans entire system for ALL NotebookLM MCP data files across 8 categories... shows categorized preview before deletion'

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access cleanup_data gives an agent:

HOW TO CONTROL CLEANUP_DATA

PolicyLayer is an MCP gateway — it sits between your AI agents and NotebookLM MCP Structured, and nothing reaches the server without passing your rules. This is the rule we recommend for cleanup_data:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cleanup_data"
  ]
}

cleanup_data disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register NotebookLM MCP Structured — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More NotebookLM MCP Structured tools

Destructive remove_notebook Dangerous — requires explicit user confirmation. Confirmation Workflow 1) User requests Destructive reset_session Reset a session Execute setup_auth Google authentication for NotebookLM access - opens a browser window for manual login to y Write add_notebook PERMISSION REQUIRED — Only when user explicitly asks to add a notebook. Conversation Wor Write close_session Close a specific session by session ID. Ask before closing if the user might still need it Write select_notebook Set a notebook as the active default (used when ask_question has no notebook_id). When T Write update_notebook Update notebook metadata based on user intent. Pattern 1) Identify target notebook and f Read get_health Get server health status including authentication state, active sessions, and configuratio

All 15 NotebookLM MCP Structured tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in NotebookLM MCP Structured → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the cleanup_data tool do? +

ULTRATHINK Deep Cleanup - Scans entire system for ALL NotebookLM MCP data files across 8 categories. Always runs in deep mode, shows categorized preview before deletion.\n\n. It is categorised as a Destructive tool in the NotebookLM MCP Structured MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cleanup_data? +

Register the NotebookLM MCP Structured MCP server in PolicyLayer and add a rule for cleanup_data: 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 Structured. Nothing to install.

What risk level is cleanup_data? +

cleanup_data is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cleanup_data? +

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

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

cleanup_data is provided by the NotebookLM MCP Structured MCP server (paolodalprato/notebooklm-mcp-structured). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every NotebookLM MCP Structured tool call.

Deterministic rules across all 15 NotebookLM MCP Structured tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN NOTEBOOKLM MCP STRUCTURED →

Free to start. No card required.

15 NotebookLM MCP Structured tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

cleanup_data

// WHAT CLEANUP_DATA ON NOTEBOOKLM MCP STRUCTURED DOES

// THE RISK

// HOW TO CONTROL CLEANUP_DATA

// EXPLORE