Delete studio artifact. IRREVERSIBLE. Requires confirm=True.
AI agents call studio_delete to permanently remove resources in NotebookLM MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes studio artifacts (generated content like audio overviews, videos, infographics, or slide decks) created within NotebookLM. Once deleted, the data cannot be recovered. The explicit 'IRREVERSIBLE' designation and confirmation requirement confirm this is a destructive action with no undo capability.
From the tool's definition Tool name is 'studio_delete' and description explicitly states 'Delete studio artifact. IRREVERSIBLE. Requires confirm=True.' The word 'IRREVERSIBLE' and 'Delete' directly indicate permanent data destruction.
Attacks that exploit this kind of access
Delete studio artifact. IRREVERSIBLE. Requires confirm=True. It is categorised as a Destructive tool in the NotebookLM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the NotebookLM MCP Server 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 MCP Server. Nothing to install.
studio_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
studio_delete is provided by the NotebookLM MCP Server MCP server (set2374/notebooklm-mcp-archived). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →