Delete an artifact.
AI agents call artifact_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 permanently removes an artifact from NotebookLM. Deletion is an irreversible operation that cannot be undone by the AI agent. While the blast radius is limited to user-owned artifacts within the NotebookLM instance (not system-wide), an AI agent misusing this could permanently destroy research work, generated study materials, or other user content. This warrants high severity and Destructive categorization.
From the tool's definition Tool name is 'artifact_delete' with description 'Delete an artifact.' The verb 'delete' is explicitly destructive and irreversible.
Attacks that exploit this kind of access
Delete an artifact. 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 artifact_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.
artifact_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 artifact_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 artifact_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.
artifact_delete 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.
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 →