List notebooks in a workspace directory
AI agents call list_notebooks to retrieve information from Databricks MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs directory listing/enumeration of notebooks, which is a read-only operation with no side effects. It retrieves data about existing notebooks but does not create, modify, delete, or execute any code. The blast radius is minimal—an agent listing notebooks cannot cause harm beyond potential information disclosure of notebook names and paths within the workspace.
From the tool's definition Tool name 'list_notebooks' and description 'List notebooks in a workspace directory' indicate a query operation that retrieves information without modifying state.
Attacks that exploit this kind of access
List notebooks in a workspace directory. It is categorised as a Read tool in the Databricks MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for list_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 Databricks MCP Server. Nothing to install.
list_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_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_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_notebooks is provided by the Databricks MCP Server MCP server (samhavens/databricks-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 →