Get permissions for a cluster with parameter: cluster_id (required)
AI agents call get_cluster_permissions to retrieve information from Databricks Permissions MCP Server 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 existing permission data for a Databricks cluster. It is a read-only operation that retrieves information (who has what access level on a cluster) without any side effects, reversible modifications, code execution, destruction, or financial impact. The 'get_' prefix and retrieval nature confirm Read category.
From the tool's definition Tool name contains 'get_' and description states 'Get permissions for a cluster' — retrieves cluster permission metadata without modifying state.
Attacks that exploit this kind of access
Get permissions for a cluster with parameter: cluster_id (required). It is categorised as a Read tool in the Databricks Permissions MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Databricks Permissions MCP Server MCP server in PolicyLayer and add a rule for get_cluster_permissions: 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 Permissions MCP Server. Nothing to install.
get_cluster_permissions 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_cluster_permissions 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_cluster_permissions. 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_cluster_permissions is provided by the Databricks Permissions MCP Server MCP server (justtryai/databricks-permissions-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 →