Delete a cell (code or markdown) from the notebook.
AI agents call delete_cell to permanently remove resources in Jlab — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of notebook cells is an irreversible operation that cannot be undone through the tool itself. While not as critical as system-level data destruction, it permanently removes user work or computational results. The high severity reflects the potential for significant data loss in an HPC research context where notebooks document critical computational workflows.
From the tool's definition Tool name 'delete_cell' and description 'Delete a cell (code or markdown) from the notebook' indicate irreversible removal of notebook content.
Attacks that exploit this kind of access
Delete a cell (code or markdown) from the notebook. It is categorised as a Destructive tool in the Jlab MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jlab MCP server in PolicyLayer and add a rule for delete_cell: 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 Jlab. Nothing to install.
delete_cell 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_cell 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_cell. 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_cell is provided by the Jlab MCP server (kdkyum/jlab-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 →