run_job · Cloudera Data Visualization MCP Server MCP

WHAT IT DOES

What run_job does on Cloudera Data Visualization MCP Server

AI agents invoke run_job to trigger actions in Cloudera Data Visualization 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 run_job needs a policy

This tool executes pre-defined jobs (likely data processing, refresh, or transformation tasks) in the Cloudera Data Visualization environment. Depending on what those jobs do, they could read data, write data, or perform other side-effecting operations.

From the tool's definition The tool 'run_job' triggers execution of scheduled jobs in Cloudera Data Visualization. The verb 'trigger' and 'rerun' indicate active execution of external operations whose effects depend on which jobs are specified as arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_job Rate-limited

run_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": {
    "run_job": {
      "limits": [
        {
          "counter": "run_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 Cloudera Data Visualization MCP Server, so you can run agents against it safely.

FAQ

Questions about run_job

What does the run_job tool do? +

Trigger a rerun of one or more CDV scheduled jobs. It is categorised as a Execute tool in the Cloudera Data Visualization 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 run_job? +

Register the Cloudera Data Visualization MCP Server MCP server in PolicyLayer and add a rule for run_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 Cloudera Data Visualization MCP Server. Nothing to install.

What risk level is run_job? +

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

Can I rate-limit run_job? +

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

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

run_job is provided by the Cloudera Data Visualization MCP Server MCP server (kevintalbert/cdv-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.