set_permissions · Databricks Permissions MCP Server MCP

WHAT IT DOES

What set_permissions does on Databricks Permissions MCP Server

AI agents use set_permissions to create or update resources in Databricks Permissions MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Databricks Permissions MCP Server environment.

WHY IT NEEDS A POLICY

Why set_permissions needs a policy

The tool creates or modifies permission configurations reversibly—permissions can be changed or reverted. This is a Write operation since it updates access control state rather than executing code (Execute), deleting data (Destructive), or moving money (Financial).

From the tool's definition Tool modifies access control by setting permissions on Databricks objects via "set_permissions" with object_type, object_id, and access_control_list parameters. Description states it "Set permissions for a Databricks object."

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_permissions Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_permissions": {
      "limits": [
        {
          "counter": "set_permissions_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Databricks Permissions MCP Server, so you can run agents against it safely.

FAQ

Questions about set_permissions

What does the set_permissions tool do? +

Set permissions for a Databricks object with parameters: object_type (required), object_id (required), access_control_list (required). It is categorised as a Write tool in the Databricks Permissions MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_permissions? +

Register the Databricks Permissions MCP Server MCP server in PolicyLayer and add a rule for 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 Permissions MCP Server. Nothing to install.

What risk level is set_permissions? +

set_permissions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_permissions? +

Yes. Add a rate_limit block to the 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.

How do I block set_permissions completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides set_permissions? +

set_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.