databricks_update_serving_endpoint

A write tool on the Databricks MCP server.

SERVERDatabricks MCP Server SOURCEpypi:databricks-sdk-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-update-serving-endpoint.md

WHAT IT DOES

What databricks_update_serving_endpoint does on Databricks MCP Server

AI agents use databricks_update_serving_endpoint to create or update resources in Databricks MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Databricks MCP Server environment.

RISK

Why databricks_update_serving_endpoint is rated Medium

The tool performs an update operation on a Databricks serving endpoint, which is a Write action that modifies configuration but is reversible. The high severity reflects that misconfigured serving endpoints could impact production ML model availability and performance. Confidence is slightly reduced because the description is empty, but the name clearly indicates an update operation on production infrastructure.

From the tool's definition Tool name 'databricks_update_serving_endpoint' indicates modification of a serving endpoint configuration. The 'update' verb signifies reversible data modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

databricks_update_serving_endpoint Rate-limited

databricks_update_serving_endpoint 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": {
    "databricks_update_serving_endpoint": {
      "limits": [
        {
          "counter": "databricks_update_serving_endpoint_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about databricks_update_serving_endpoint

What does the databricks_update_serving_endpoint tool do? +

databricks_update_serving_endpoint is a write tool on the Databricks MCP Server MCP server. It is categorised as a Write tool in the Databricks 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 databricks_update_serving_endpoint? +

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

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

Can I rate-limit databricks_update_serving_endpoint? +

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

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

databricks_update_serving_endpoint 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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →