jupyter_start_kernel · Multi-Tool MCP Server MCP

WHAT IT DOES

What jupyter_start_kernel does on Multi-Tool MCP Server

AI agents invoke jupyter_start_kernel to trigger actions in Multi-Tool MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why jupyter_start_kernel needs a policy

Starting a Jupyter kernel allows execution of arbitrary code in the server's context. While not immediately destructive, it grants an AI agent the ability to run shell commands, modify files, and access system resources. The severity is high because a compromised or misdirected AI could use this to pivot to destructive actions, data exfiltration, or lateral movement.

From the tool's definition 'Start a new Jupyter kernel' — Jupyter kernels execute arbitrary Python code and system commands. This tool initiates a computational environment capable of running code with the privileges of the server process.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jupyter_start_kernel Rate-limited

jupyter_start_kernel stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jupyter_start_kernel": {
      "limits": [
        {
          "counter": "jupyter_start_kernel_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about jupyter_start_kernel

What does the jupyter_start_kernel tool do? +

Start a new Jupyter kernel. It is categorised as a Execute tool in the Multi-Tool MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on jupyter_start_kernel? +

Register the Multi-Tool MCP Server MCP server in PolicyLayer and add a rule for jupyter_start_kernel: 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 Multi-Tool MCP Server. Nothing to install.

What risk level is jupyter_start_kernel? +

jupyter_start_kernel is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit jupyter_start_kernel? +

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

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

jupyter_start_kernel is provided by the Multi-Tool MCP Server MCP server (shawn-falconbury/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.