update_service_principal

WHAT IT DOES

What update_service_principal does on Databricks Permissions MCP Server

AI agents use update_service_principal 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_service_principal needs a policy

This tool modifies service principal properties and permissions (allow_cluster_create flag), which affects IAM/access control. Updates are reversible (can be undone via subsequent updates), placing this in Write rather than Destructive. However, the blast radius is high because modifying service principal permissions could grant or restrict cluster creation privileges across multiple workloads and users.

From the tool's definition Tool name 'update_service_principal' and description 'Update a service principal' indicate modification of existing security principal configuration. Parameters include 'allow_cluster_create' which controls access privileges.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_service_principal Rate-limited

update_service_principal 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_service_principal": {
      "limits": [
        {
          "counter": "update_service_principal_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_service_principal

What does the update_service_principal tool do? +

Update a service principal with parameters: id (required), display_name (optional), allow_cluster_create (optional). 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_service_principal? +

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

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

Can I rate-limit update_service_principal? +

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

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

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