update_permissions · Databricks Permissions MCP Server MCP

WHAT IT DOES

What update_permissions does on Databricks Permissions MCP Server

AI agents use update_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 update_permissions needs a policy

This tool creates or modifies permissions reversibly—a core Write operation. While permission changes affect security posture and could have significant blast radius (high severity), they are not irreversible deletions (Destructive) or financial transactions. An AI agent misusing this tool could grant unintended access to sensitive Databricks resources, but the changes can be reverted by updating permissions again.

From the tool's definition Tool name 'update_permissions' and description indicate it modifies access control lists for Databricks objects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_permissions Rate-limited

update_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": {
    "update_permissions": {
      "limits": [
        {
          "counter": "update_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 update_permissions

What does the update_permissions tool do? +

Update 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 update_permissions? +

Register the Databricks Permissions MCP Server MCP server in PolicyLayer and add a rule for update_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 update_permissions? +

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

Can I rate-limit update_permissions? +

Yes. Add a rate_limit block to the update_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 update_permissions completely? +

Set action: deny in the PolicyLayer policy for update_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 update_permissions? +

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