studio_delete

THE RISK

Critical Risk

Why studio_delete needs a policy

The tool performs an irreversible deletion operation on a studio artifact within NotebookLM. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While the blast radius is limited to a single artifact rather than bulk data, deletion of user-created content (such as generated flashcards, mind maps, infographics, or data tables) represents a…

From the tool's definition Tool name 'studio_delete' with description 'Delete a studio artifact' explicitly performs deletion, which is irreversible.

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

POLICY

How to control studio_delete

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 studio_delete:

policy.json

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

studio_delete 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 — 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

Related tools and policies

More Notebooklm tools

Destructive mind_map_delete Delete a Mind Map from a notebook Destructive notebook_delete Delete a notebook permanently. IRREVERSIBLE. Destructive source_delete Delete a source permanently. IRREVERSIBLE. Execute research_start Start web or Drive research to find NEW sources. Workflow: research_start → research_poll Execute audio_overview_create Generate an Audio Overview (podcast) for the notebook Execute mind_map_generate Generate a Mind Map JSON from notebook sources Execute video_overview_create Generate a Video Overview for the notebook Write data_table_create Generate a data table from notebook sources

All 29 Notebooklm tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Notebooklm → 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.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about studio_delete

What does the studio_delete tool do? +

Delete a studio artifact. It is categorised as a Destructive tool in the Notebooklm 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 studio_delete? +

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

What risk level is studio_delete? +

studio_delete 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 studio_delete? +

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

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

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

Enforce policy on every Notebooklm tool call.

Start from Notebooklm, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →