AI agents invoke start_new_notebook to trigger actions in Jlab. 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.
This tool triggers external operations (kernel startup, session initialization on remote HPC infrastructure) whose effects depend on subsequent arguments and usage. While it doesn't directly execute code itself, it establishes the execution context for arbitrary computations on privileged GPU resources within a SLURM cluster.
From the tool's definition Tool 'start_new_notebook' initiates a new kernel and notebook session on GPU-accelerated SLURM-managed HPC resources. The description indicates it 'start[s] kernel, create[s] notebook,' which prepares a computational environment for arbitrary code execution.
Attacks that exploit this kind of access
Start a new session: start kernel, create notebook. It is categorised as a Execute tool in the Jlab MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jlab MCP server in PolicyLayer and add a rule for start_new_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 Jlab. Nothing to install.
start_new_notebook is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_new_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.
Set action: deny in the PolicyLayer policy for start_new_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.
start_new_notebook is provided by the Jlab MCP server (kdkyum/jlab-mcp). 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 →