mcp_upload_sample_py_to_databricks

WHAT IT DOES

What mcp_upload_sample_py_to_databricks does on Databricks MCP Server

AI agents use mcp_upload_sample_py_to_databricks 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.

WHY IT NEEDS A POLICY

Why mcp_upload_sample_py_to_databricks needs a policy

This tool creates or modifies a file in Databricks workspace (reversible write operation). While the fixed destination path and hardcoded content limit flexibility, it remains Write rather than Execute because it only stores code without running it.

From the tool's definition Upload a hardcoded Python string as a .py file to Databricks workspace — the tool creates a new file in Databricks, a reversible operation. The description explicitly states 'Upload...as a .py file', confirming file creation/modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mcp_upload_sample_py_to_databricks Rate-limited

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Databricks MCP Server, so you can run agents against it safely.

FAQ

Questions about mcp_upload_sample_py_to_databricks

What does the mcp_upload_sample_py_to_databricks tool do? +

Upload a hardcoded Python string as a .py file to Databricks workspace at /Users/stephen.hsu@databricks.com/claude_generated_folder/sample_claude_upload.py. 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 mcp_upload_sample_py_to_databricks? +

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

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

Can I rate-limit mcp_upload_sample_py_to_databricks? +

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

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

mcp_upload_sample_py_to_databricks is provided by the Databricks MCP Server MCP server (stephenjhsu/databricks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.