cell_add
AI agents use cell_add to create or update resources in JupyterMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your JupyterMCP environment.
The tool creates new notebook cells, which is a write operation that modifies notebook structure reversibly. While the description is empty, context from the server description and sibling tools confirms this is a cell creation function. Severity is medium because added cells could introduce unwanted code or configuration, but the operation is reversible (unlike destructive operations).
From the tool's definition Tool is named 'cell_add' and belongs to a server that 'enables AI agents to create, read, edit, and execute Jupyter notebook cells'.
Attacks that exploit this kind of access
cell_add. It is categorised as a Write tool in the JupyterMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jupyter MCP server in PolicyLayer and add a rule for cell_add: 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 JupyterMCP. Nothing to install.
cell_add 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 cell_add 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 cell_add. 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.
cell_add is provided by the Jupyter MCP server (try3d/jupytermcp). 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 →