Create a new Jupyter notebook
AI agents use jupyter_create_notebook to create or update resources in Multi-Tool MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Multi-Tool MCP Server environment.
Creating a Jupyter notebook is a write operation that creates new data/files on the filesystem. While reversible (the file can be deleted), the tool modifies state. Severity is high because Jupyter notebooks can contain and execute arbitrary Python code, and creating notebooks could be part of an attack chain to set up malicious code execution infrastructure.
From the tool's definition Tool name 'jupyter_create_notebook' and description 'Create a new Jupyter notebook' indicate file system creation that modifies the filesystem state by adding a new notebook resource.
Attacks that exploit this kind of access
Create a new Jupyter notebook. It is categorised as a Write tool in the Multi-Tool MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Multi-Tool MCP Server MCP server in PolicyLayer and add a rule for jupyter_create_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 Multi-Tool MCP Server. Nothing to install.
jupyter_create_notebook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the jupyter_create_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 jupyter_create_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.
jupyter_create_notebook 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 →