ipynb_split_notebook · Jupyter Editor MCP: Risk & Policy

WHAT IT DOES

What ipynb_split_notebook does on Jupyter Editor

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

WHY IT NEEDS A POLICY

Why ipynb_split_notebook needs a policy

Based on the tool name, 'ipynb_split_notebook' likely splits a Jupyter notebook into multiple notebooks, which is a write/create operation producing new files. This could also potentially modify or fragment the original notebook. Given the server context of editing notebooks and sibling tools that write/modify notebooks, Write is the most likely category.

From the tool's definition Tool name: ipynb_split_notebook; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ipynb_split_notebook Rate-limited

ipynb_split_notebook 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": {
    "ipynb_split_notebook": {
      "limits": [
        {
          "counter": "ipynb_split_notebook_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 Jupyter Editor, so you can run agents against it safely.

FAQ

Questions about ipynb_split_notebook

What does the ipynb_split_notebook tool do? +

ipynb_split_notebook. It is categorised as a Write tool in the Jupyter Editor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ipynb_split_notebook? +

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

What risk level is ipynb_split_notebook? +

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

Can I rate-limit ipynb_split_notebook? +

Yes. Add a rate_limit block to the ipynb_split_notebook 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 ipynb_split_notebook completely? +

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

ipynb_split_notebook is provided by the Jupyter Editor MCP server (jsamuel1/jupyter-editor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.