List all active Jupyter notebook sessions
AI agents call jupyter_list_sessions to retrieve information from Multi-Tool MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation to enumerate active Jupyter sessions. It has no side effects, does not execute code, does not modify data, and does not delete resources. The blast radius of misuse is minimal—an attacker could learn which notebooks are running but cannot directly compromise them through this tool alone. Classified as Read with low severity.
From the tool's definition Tool name 'jupyter_list_sessions' and description 'List all active Jupyter notebook sessions' indicate a query operation that retrieves information about running sessions without modifying or executing code.
Attacks that exploit this kind of access
List all active Jupyter notebook sessions. It is categorised as a Read tool in the Multi-Tool MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Multi-Tool MCP Server MCP server in PolicyLayer and add a rule for jupyter_list_sessions: 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.
jupyter_list_sessions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the jupyter_list_sessions 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 jupyter_list_sessions. 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.
jupyter_list_sessions 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →