jupyter_create_session · Multi-Tool MCP Server MCP

WHAT IT DOES

What jupyter_create_session does on Multi-Tool MCP Server

AI agents invoke jupyter_create_session 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_create_session needs a policy

Creating a Jupyter session starts a kernel, which is a live code execution environment. Once a kernel is running, arbitrary code can be executed in it. The act of starting the kernel itself initiates an external process with execution capabilities, making this an Execute-category action with high severity since it enables arbitrary code execution in a persistent environment.

From the tool's definition Create a new session for a notebook (starts a kernel attached to the notebook)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jupyter_create_session Rate-limited

jupyter_create_session 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_create_session": {
      "limits": [
        {
          "counter": "jupyter_create_session_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_create_session

What does the jupyter_create_session tool do? +

Create a new session for a notebook (starts a kernel attached to the notebook). 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_create_session? +

Register the Multi-Tool MCP Server MCP server in PolicyLayer and add a rule for jupyter_create_session: 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_create_session? +

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

Can I rate-limit jupyter_create_session? +

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

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

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