AI agents use edit_cell to create or update resources in Jlab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jlab environment.
The tool modifies cell contents in a JupyterLab session running on GPU-accelerated HPC nodes. This is reversible (Write rather than Destructive), but carries high severity because: (1) modified cells can be executed to run arbitrary code on HPC infrastructure, (2) it could alter scientific computations or data processing pipelines, and (3) the blast radius extends to shared cluster resources.
From the tool's definition Tool name 'edit_cell' combined with sibling tools 'execute_code', 'run_cell', and 'delete_cell' in a Jupyter/HPC execution environment. While the description is empty, the context strongly indicates this modifies notebook cell content.
Attacks that exploit this kind of access
edit_cell. It is categorised as a Write tool in the Jlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jlab MCP server in PolicyLayer and add a rule for edit_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.
edit_cell is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the edit_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 edit_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.
edit_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 →