databricks_get_user

A read tool on the Databricks MCP server.

SERVERDatabricks MCP Server SOURCEpypi:databricks-sdk-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-get-user.md

WHAT IT DOES

What databricks_get_user does on Databricks MCP Server

AI agents call databricks_get_user to retrieve information from Databricks MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why databricks_get_user is rated Low

The 'get' prefix strongly suggests a read operation that retrieves user metadata or details. No side effects are expected—the tool queries existing user data. Confidence is moderated from higher due to the empty description, which prevents confirmation of exact behavior, scope, or whether any sensitive data exposure might elevate severity slightly.

From the tool's definition Tool name 'databricks_get_user' contains the verb 'get', which typically retrieves data without modification. The tool appears designed to fetch user information from Databricks.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs databricks_get_user safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Databricks MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For databricks_get_user, this is the rule to start with:

databricks_get_user Allowed

databricks_get_user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "databricks_get_user": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Databricks MCP Server, apply this rule, and every databricks_get_user call is checked against it from then on.

FAQ

Questions about databricks_get_user

What does the databricks_get_user tool do? +

databricks_get_user is a read tool on the Databricks MCP Server MCP server. It is categorised as a Read tool in the Databricks MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on databricks_get_user? +

Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for databricks_get_user: 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 MCP Server. Nothing to install.

What risk level is databricks_get_user? +

databricks_get_user is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit databricks_get_user? +

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

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

databricks_get_user is provided by the Databricks MCP Server MCP server (pypi:databricks-sdk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Databricks MCP Server, and thousands of servers like it.

This server

All 262 Databricks MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →