List local .ipynb notebooks under COLAB_MCP_ROOT.
AI agents call list_local_notebooks to retrieve information from Pypi:colab Drive without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of existing notebooks from a local directory. It performs read-only introspection with no ability to create, modify, delete, execute, or cause financial impact. The blast radius of misuse is minimal—an agent can only discover what notebooks exist locally, which is informational only.
From the tool's definition Tool name 'list_local_notebooks' and description 'List local .ipynb notebooks under COLAB_MCP_ROOT' indicate a retrieval/enumeration operation with no modification or side effects.
Attacks that exploit this kind of access
List local .ipynb notebooks under COLAB_MCP_ROOT. It is categorised as a Read tool in the Pypi:colab Drive MCP Server, which means it retrieves data without modifying state.
Register the Pypi:colab Drive MCP server in PolicyLayer and add a rule for list_local_notebooks: 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 Pypi:colab Drive. Nothing to install.
list_local_notebooks 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 list_local_notebooks 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 list_local_notebooks. 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.
list_local_notebooks is provided by the Pypi:colab Drive MCP server (yummytastycode/colab-drive-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 →