ipynb_search_replace_all · Jupyter Editor MCP: Risk & Policy

WHAT IT DOES

What ipynb_search_replace_all does on Jupyter Editor

AI agents use ipynb_search_replace_all 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_search_replace_all needs a policy

The name suggests a bulk search-and-replace operation on Jupyter notebooks, which would modify data (Write). However, the description is empty, so the exact behavior is uncertain. 'Replace all' operations can have significant blast radius if misapplied across many notebooks, but the operation is likely reversible. Confidence is lowered due to the empty description.

From the tool's definition Tool name: ipynb_search_replace_all — 'search_replace_all' implies a global find-and-replace operation across notebook content.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ipynb_search_replace_all Rate-limited

ipynb_search_replace_all 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_search_replace_all": {
      "limits": [
        {
          "counter": "ipynb_search_replace_all_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_search_replace_all

What does the ipynb_search_replace_all tool do? +

ipynb_search_replace_all. 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_search_replace_all? +

Register the Jupyter Editor MCP server in PolicyLayer and add a rule for ipynb_search_replace_all: 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_search_replace_all? +

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

Can I rate-limit ipynb_search_replace_all? +

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

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

ipynb_search_replace_all 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.