Get basic information about a Jupyter notebook.
AI agents call get_notebook_info to retrieve information from Jupyter Notebook MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata and information about a notebook without executing code, modifying cells, or deleting anything. It is a pure read operation with minimal risk. Even if misused by an agent, it only exposes notebook structure and metadata, causing no side effects.
From the tool's definition Tool name is 'get_notebook_info' and description states it 'Get[s] basic information about a Jupyter notebook' — this is a retrieval operation with no modification or execution.
Attacks that exploit this kind of access
Get basic information about a Jupyter notebook. It is categorised as a Read tool in the Jupyter Notebook MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jupyter Notebook MCP Server MCP server in PolicyLayer and add a rule for get_notebook_info: 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 Notebook MCP Server. Nothing to install.
get_notebook_info 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 get_notebook_info 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 get_notebook_info. 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.
get_notebook_info is provided by the Jupyter Notebook MCP Server MCP server (shwetalsoni/jupyter-notebook-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 →