Moves a cell to a different position
AI agents use notebook_move_cell to create or update resources in Claude Code Notebook MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Code Notebook MCP environment.
Moving a cell changes the notebook's structure and cell ordering, which is a write operation that modifies data. While reversible (unlike deletion), it alters the state of the notebook and could affect downstream execution if cells have dependencies.
From the tool's definition The tool "moves a cell to a different position" within a notebook, modifying the order and structure of notebook content. This is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access notebook_move_cell gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code Notebook MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for notebook_move_cell:
{
"version": "1",
"default": "deny",
"tools": {
"notebook_move_cell": {
"limits": [
{
"counter": "notebook_move_cell_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} notebook_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.
Free to start. No card required.
Moves a cell to a different position. It is categorised as a Write tool in the Claude Code Notebook MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Code Notebook MCP server in PolicyLayer and add a rule for notebook_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 Claude Code Notebook MCP. Nothing to install.
notebook_move_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 notebook_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.
Set action: deny in the PolicyLayer policy for notebook_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.
notebook_move_cell is provided by the Claude Code Notebook MCP server (mstampfer/claude-code-notebook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Code Notebook MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Claude Code Notebook MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.