databricks_list_database_roles
A read tool on the Databricks MCP server.
This record as markdown: /tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-list-database-roles.md
What databricks_list_database_roles does on Databricks MCP Server
AI agents call databricks_list_database_roles to retrieve information from Databricks MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why databricks_list_database_roles is rated Low
The 'list' prefix indicates this tool queries and returns a collection of database roles from Databricks. This is a read-only operation with no side effects. Although the description is empty, the naming convention is clear and consistent with other list-based tools on the server (e.g., databricks_list_*). Risk is low because listing roles does not modify data or trigger external operations.
From the tool's definition Tool name 'databricks_list_database_roles' contains 'list', a standard Read operation verb that retrieves or enumerates existing data without modification.
Attacks that exploit this kind of access
The rule that runs databricks_list_database_roles safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Databricks MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For databricks_list_database_roles, this is the rule to start with:
databricks_list_database_roles is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Databricks MCP Server, apply this rule, and every databricks_list_database_roles call is checked against it from then on.
Questions about databricks_list_database_roles
databricks_list_database_roles is a read tool on the Databricks MCP Server MCP server. 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 databricks_list_database_roles: 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.
databricks_list_database_roles 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 databricks_list_database_roles 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 databricks_list_database_roles. 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.
databricks_list_database_roles is provided by the Databricks MCP Server MCP server (pypi:databricks-sdk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Databricks MCP Server, and thousands of servers like it.
This server
Across the catalogue