Save the current session state to a notebook.
AI agents use jupyter_save_notebook to create or update resources in ML Jupyter MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ML Jupyter MCP environment.
This tool creates or modifies notebook files, which is a Write operation. While reversible, it persists code execution state to storage, potentially capturing sensitive computational results, variable values, or imported credentials.
From the tool's definition Tool name 'jupyter_save_notebook' and description 'Save the current session state to a notebook' indicate creation/modification of notebook files on disk. The action is reversible (files can be overwritten or deleted).
Attacks that exploit this kind of access
Save the current session state to a notebook. It is categorised as a Write tool in the ML Jupyter MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ML Jupyter MCP server in PolicyLayer and add a rule for jupyter_save_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 ML Jupyter MCP. Nothing to install.
jupyter_save_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_save_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_save_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_save_notebook is provided by the ML Jupyter MCP server (mayank-ketkar-sf/claudejupy). 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 →