notebook_get_info

THE RISK

Low Risk

Why notebook_get_info needs a policy

This tool only queries and returns metadata about a notebook without creating, modifying, executing, or deleting anything. It is a read-only operation with no side effects or blast radius if misused by an AI agent.

From the tool's definition Tool name is 'notebook_get_info' and description states it 'Retrieves general information (cell count, metadata, kernel, language info)' — a pure information retrieval operation with no modification or execution.

Documented attack patterns abuse exactly the kind of access notebook_get_info gives an agent:

POLICY

How to control notebook_get_info

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code Notebook MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for notebook_get_info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "notebook_get_info": {}
  }
}

notebook_get_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Claude Code Notebook MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Claude Code Notebook MCP tools

Destructive notebook_delete Deletes an existing notebook file Destructive notebook_delete_cell Deletes a specific cell Write notebook_clear_all_outputs Clears outputs and execution counts for all code cells Write notebook_clear_cell_outputs Clears the outputs and execution count of a specific cell Write notebook_add_cell Adds a new code or markdown cell after a specified index Write notebook_bulk_add_cells Adds multiple cells to a notebook in a single operation Write notebook_change_cell_type Changes a cell Write notebook_create Creates a new, empty notebook file

All 29 Claude Code Notebook MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about notebook_get_info

What does the notebook_get_info tool do? +

Retrieves general information (cell count, metadata, kernel, language info). It is categorised as a Read tool in the Claude Code Notebook MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on notebook_get_info? +

Register the Claude Code Notebook MCP server in PolicyLayer and add a rule for notebook_get_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 Claude Code Notebook MCP. Nothing to install.

What risk level is notebook_get_info? +

notebook_get_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit notebook_get_info? +

Yes. Add a rate_limit block to the notebook_get_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.

How do I block notebook_get_info completely? +

Set action: deny in the PolicyLayer policy for notebook_get_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.

What MCP server provides notebook_get_info? +

notebook_get_info is provided by the Claude Code Notebook MCP server (mstampfer/claude-code-notebook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Code Notebook MCP tool call.

Start from Claude Code Notebook MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →