Get details of a service principal with parameter: id (required)
AI agents call get_service_principal to retrieve information from Databricks Permissions MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a service principal (a non-human identity used for authentication and authorization in Databricks). While it is fundamentally a read operation with no side effects, service principals can be sensitive resources whose details (including associated permissions, credentials, or access levels) could be misused if an AI agent queries them maliciously.
From the tool's definition Tool name 'get_service_principal' and description 'Get details of a service principal' indicate a read/retrieval operation with no modification. However, service principal details may include sensitive credential information or authorization metadata.
Attacks that exploit this kind of access
Get details of a service principal with parameter: id (required). It is categorised as a Read tool in the Databricks Permissions MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Databricks Permissions MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_service_principal is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →