create_service_principal

WHAT IT DOES

What create_service_principal does on Databricks Permissions MCP Server

AI agents use create_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 create_service_principal needs a policy

This tool creates a new service principal—a reversible operation that modifies Databricks' identity and access control system. While not destructive (can be deleted via delete_service_principal), it is a Write operation that establishes a new security principal with potential elevated privileges (allow_cluster_create).

From the tool's definition Tool performs 'create' operation on a service principal, which creates a new identity/account in Databricks with optional cluster creation permissions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_service_principal Rate-limited

create_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": {
    "create_service_principal": {
      "limits": [
        {
          "counter": "create_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 create_service_principal

What does the create_service_principal tool do? +

Create a service principal with parameters: display_name (required), application_id (required), 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 create_service_principal? +

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

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

Can I rate-limit create_service_principal? +

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

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

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