Delete a Jupyter notebook or file
AI agents call jupyter_delete_notebook to permanently remove resources in Multi-Tool MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation on files/notebooks. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push)'. Severity is high because notebook deletion cannot be undone and could result in loss of important code, analysis, or research.
From the tool's definition Tool name contains 'delete' and description states 'Delete a Jupyter notebook or file' — this irreversibly removes data.
Attacks that exploit this kind of access
Delete a Jupyter notebook or file. It is categorised as a Destructive tool in the Multi-Tool MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Multi-Tool MCP Server MCP server in PolicyLayer and add a rule for jupyter_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 Multi-Tool MCP Server. Nothing to install.
jupyter_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 jupyter_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 jupyter_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.
jupyter_delete_notebook is provided by the Multi-Tool MCP Server MCP server (shawn-falconbury/mcp-server). 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 →