databricks_get_run

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-run.md

What databricks_get_run does on Databricks MCP Server

AI agents call databricks_get_run 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.

Why databricks_get_run is rated Low

Despite the empty description, the 'get_' prefix is a strong indicator of a read operation that retrieves run metadata or status from Databricks. This has no capability to modify, delete, or execute code. Confidence is moderately high but not maximal due to the absent description; however, the naming convention is reliable. Severity is low because retrieval operations pose minimal risk if misused by an AI agent.

From the tool's definition Tool name 'databricks_get_run' indicates retrieval of run information. The name structure aligns with 'get' operations which are read-only queries without side effects.

Questions about databricks_get_run

What does the databricks_get_run tool do? +

databricks_get_run 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_run? +

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

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

Can I rate-limit databricks_get_run? +

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

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Databricks MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.