update_share_permissions

WHAT IT DOES

What update_share_permissions does on Databricks Permissions MCP Server

AI agents use update_share_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_share_permissions needs a policy

This tool modifies access control permissions for Databricks shares, which is a reversible write operation. While it doesn't delete or create new shares, it alters security-relevant metadata (permissions). Severity is high because misconfiguration could grant unintended access to sensitive data assets across an organization, but it remains Write rather than Destructive since permission changes can be reverted.

From the tool's definition Tool name 'update_share_permissions' and description indicate modification of permissions via 'Update permissions' action. The 'changes' parameter enables reversible updates to access control settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_share_permissions Rate-limited

update_share_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_share_permissions": {
      "limits": [
        {
          "counter": "update_share_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_share_permissions

What does the update_share_permissions tool do? +

Update permissions for a share with parameters: name (required), changes (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_share_permissions? +

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

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

Can I rate-limit update_share_permissions? +

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

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

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