move_cell · MCP Jupyter Complete MCP: Risk & Policy

WHAT IT DOES

What move_cell does on MCP Jupyter Complete

AI agents use move_cell to create or update resources in MCP Jupyter Complete — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Jupyter Complete environment.

WHY IT NEEDS A POLICY

Why move_cell needs a policy

Moving a cell is a reversible modification operation that changes the notebook structure but does not delete data (excluding Destructive category) or execute code (excluding Execute category). The action is Write-class because it modifies notebook state in a way that can be undone by moving the cell back to its original position.

From the tool's definition Tool description states 'Move a cell from one position to another', which modifies the structure and order of notebook content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_cell Rate-limited

move_cell stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_cell": {
      "limits": [
        {
          "counter": "move_cell_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Jupyter Complete, so you can run agents against it safely.

FAQ

Questions about move_cell

What does the move_cell tool do? +

Move a cell from one position to another. It is categorised as a Write tool in the MCP Jupyter Complete MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on move_cell? +

Register the MCP Jupyter Complete MCP server in PolicyLayer and add a rule for move_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 MCP Jupyter Complete. Nothing to install.

What risk level is move_cell? +

move_cell is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit move_cell? +

Yes. Add a rate_limit block to the move_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.

How do I block move_cell completely? +

Set action: deny in the PolicyLayer policy for move_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.

What MCP server provides move_cell? +

move_cell is provided by the MCP Jupyter Complete MCP server (tofunori/mcp-jupyter-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.