get_run_output

Get the output and metadata of a single task run with parameter: run_id (string, required)

SERVERDatabricks MCP Server SOURCEandresgarciasobrado91/databricks-mcp-server

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/andresgarciasobrado91-databricks-mcp-server/get-run-output.md

WHAT IT DOES

What get_run_output does on Databricks MCP Server

AI agents call get_run_output 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 get_run_output is rated Low

This tool queries and retrieves existing data (run output and metadata) without modifying, deleting, or executing anything. It is a straightforward read operation similar to list_jobs, get_cluster, and get_job on the same server. The blast radius of misuse is minimal—an attacker gains visibility into past task execution results but cannot alter infrastructure or data.

From the tool's definition Tool is named "get_run_output" and described as retrieving "the output and metadata of a single task run". The verb "get" and the retrieval-only nature of fetching run output and metadata indicate a read operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_run_output 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 get_run_output, this is the rule to start with:

get_run_output Allowed

get_run_output 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": {
    "get_run_output": {}
  }
}

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 get_run_output call is checked against it from then on.

FAQ

Questions about get_run_output

What does the get_run_output tool do? +

Get the output and metadata of a single task run with parameter: run_id (string, required). 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 get_run_output? +

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

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

Can I rate-limit get_run_output? +

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

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

get_run_output is provided by the Databricks MCP Server MCP server (andresgarciasobrado91/databricks-mcp-server). 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 15 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 →