Get Jupyter Notebook (.ipynb) or cell metadata.
AI agents call ipynb_get_metadata to retrieve information from Jupyter Editor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata from Jupyter notebooks or cells. It performs a read-only query operation with no side effects, no code execution, no data modification, and no destructive actions. The blast radius of misuse is minimal—an attacker could only learn about notebook structure or properties, not modify data or execute arbitrary code.
From the tool's definition Tool name 'ipynb_get_metadata' and description 'Get Jupyter Notebook (.ipynb) or cell metadata' indicate retrieval of metadata without modification, deletion, or execution.
Attacks that exploit this kind of access
Get Jupyter Notebook (.ipynb) or cell metadata. It is categorised as a Read tool in the Jupyter Editor MCP Server, which means it retrieves data without modifying state.
Register the Jupyter Editor MCP server in PolicyLayer and add a rule for ipynb_get_metadata: 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 Jupyter Editor. Nothing to install.
ipynb_get_metadata 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 ipynb_get_metadata 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 ipynb_get_metadata. 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.
ipynb_get_metadata is provided by the Jupyter Editor MCP server (jsamuel1/jupyter-editor-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 →