databricks_create_recipient

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-create-recipient.md

WHAT IT DOES

What databricks_create_recipient does on Databricks MCP Server

AI agents use databricks_create_recipient 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_create_recipient is rated Medium

The 'create_' prefix indicates data creation, which is a Write operation. It is reversible (recipients can be deleted). Severity is medium because creating recipients in a data sharing context could affect access controls and data governance, but the operation itself is not destructive or irreversible.

From the tool's definition Tool name 'databricks_create_recipient' indicates creation of a recipient object. Description is empty, but context from sibling tools (create_catalog, create_cluster, create_alert, create_app) on the Databricks MCP server suggests this performs a data…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

databricks_create_recipient Rate-limited

databricks_create_recipient 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_create_recipient": {
      "limits": [
        {
          "counter": "databricks_create_recipient_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_create_recipient call is checked against it from then on.

FAQ

Questions about databricks_create_recipient

What does the databricks_create_recipient tool do? +

databricks_create_recipient 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_create_recipient? +

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

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

Can I rate-limit databricks_create_recipient? +

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

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

databricks_create_recipient 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

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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