databricks_delete_serving_endpoint

Delete a serving endpoint.

SERVERDatabricks MCP Server SOURCEpypi:databricks-sdk-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What databricks_delete_serving_endpoint does on Databricks MCP Server

AI agents call databricks_delete_serving_endpoint to permanently remove resources in Databricks MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why databricks_delete_serving_endpoint is rated Critical

Deleting a serving endpoint is a destructive action that cannot be undone. It removes a running inference service, terminating access to it and potentially disrupting dependent applications. This is irreversible without manual recreation. While not financial, it causes operational harm with high blast radius if triggered unintentionally by an AI agent.

From the tool's definition Tool name includes 'delete' and description states 'Delete a serving endpoint' - irreversible removal of a deployed service endpoint.

Questions about databricks_delete_serving_endpoint

What does the databricks_delete_serving_endpoint tool do? +

Delete a serving endpoint. It is categorised as a Destructive tool in the Databricks MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on databricks_delete_serving_endpoint? +

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

databricks_delete_serving_endpoint is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit databricks_delete_serving_endpoint? +

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

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

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

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.