mcp_submit_code · Databricks MCP Server MCP: Risk & Policy

WHAT IT DOES

What mcp_submit_code does on Databricks MCP Server

AI agents invoke mcp_submit_code to trigger actions in Databricks MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why mcp_submit_code needs a policy

The name 'submit_code' suggests this tool submits code for execution, likely on a Databricks cluster given the server context. The description is empty, which lowers confidence. Given sibling tools that interact with Databricks clusters and jobs, this tool most plausibly executes code remotely. Execute is the most appropriate category.

From the tool's definition Tool name: mcp_submit_code — 'submit_code' strongly implies executing or running code

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mcp_submit_code Rate-limited

mcp_submit_code stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_submit_code": {
      "limits": [
        {
          "counter": "mcp_submit_code_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_submit_code

What does the mcp_submit_code tool do? +

mcp_submit_code. It is categorised as a Execute tool in the Databricks MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mcp_submit_code? +

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

mcp_submit_code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit mcp_submit_code? +

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

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

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