databricks_set_permissions
A write tool on the Databricks MCP server.
This record as markdown: /tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-set-permissions.md
What databricks_set_permissions does on Databricks MCP Server
AI agents use databricks_set_permissions to create or update resources in Databricks MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Databricks MCP Server environment.
Why databricks_set_permissions is rated Medium
Setting permissions modifies access control rules and is reversible (permissions can be changed again), placing it in the Write category rather than Destructive. However, misuse could grant excessive access to sensitive data or resources, justifying 'high' severity.
From the tool's definition Tool name 'databricks_set_permissions' indicates modification of access control settings. The 'set' verb indicates state change. No description provided, but permission management is inherently a write operation that affects who can access resources.
Attacks that exploit this kind of access
The rule that runs databricks_set_permissions 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_set_permissions, this is the rule to start with:
databricks_set_permissions stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_set_permissions call is checked against it from then on.
Questions about databricks_set_permissions
databricks_set_permissions is a write tool on the Databricks MCP Server MCP server. It is categorised as a Write tool in the Databricks MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for databricks_set_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 MCP Server. Nothing to install.
databricks_set_permissions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the databricks_set_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 databricks_set_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.
databricks_set_permissions 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