submit_job · Dataproc MCP Server MCP: Risk & Policy

WHAT IT DOES

What submit_job does on Dataproc MCP Server

AI agents invoke submit_job to trigger actions in Dataproc 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 submit_job needs a policy

The tool name 'submit_job' strongly implies triggering execution of a job (Spark, PySpark, Hive, etc.) on a Dataproc cluster. This is an Execute-category action as it runs external compute workloads. The description is empty, reducing confidence slightly, but the server context makes the intent clear. Misuse could launch expensive or long-running compute jobs, hence high severity.

From the tool's definition Tool name 'submit_job' on a server that 'Supports cluster creation/deletion, job submission (Spark, PySpark, Hive, etc.), and serverless batch operations'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_job Rate-limited

submit_job 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": {
    "submit_job": {
      "limits": [
        {
          "counter": "submit_job_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 Dataproc MCP Server, so you can run agents against it safely.

FAQ

Questions about submit_job

What does the submit_job tool do? +

submit_job. It is categorised as a Execute tool in the Dataproc 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 submit_job? +

Register the Dataproc MCP Server MCP server in PolicyLayer and add a rule for submit_job: 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 Dataproc MCP Server. Nothing to install.

What risk level is submit_job? +

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

Can I rate-limit submit_job? +

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

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

submit_job is provided by the Dataproc MCP Server MCP server (warrenzhu25/dataproc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.