Delete a notebook by ID. This action is irreversible.
AI agents call delete_notebook to permanently remove resources in Zeppelin — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes a notebook and its contents from the Zeppelin server. While not directly involving data exfiltration or external system compromise, the permanent loss of potentially critical data analysis work and notebooks represents a high-blast-radius action. The tool belongs in the Destructive category per the classification framework, as it cannot be undone and results in data loss.
From the tool's definition Tool description explicitly states "Delete a notebook by ID. This action is irreversible." The verb "delete" combined with "irreversible" classification indicates permanent removal of data.
Attacks that exploit this kind of access
Delete a notebook by ID. This action is irreversible. It is categorised as a Destructive tool in the Zeppelin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Zeppelin MCP server in PolicyLayer and add a rule for delete_notebook: 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 Zeppelin. Nothing to install.
delete_notebook 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 delete_notebook 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 delete_notebook. 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.
delete_notebook is provided by the Zeppelin MCP server (mihneamanolache/zeppelin-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 →