cancel_running_jobs · Dataiku DSS MCP Server MCP

WHAT IT DOES

What cancel_running_jobs does on Dataiku DSS MCP Server

AI agents invoke cancel_running_jobs to trigger actions in Dataiku DSS 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 cancel_running_jobs needs a policy

Cancelling running jobs/scenarios is an operational action that interrupts active execution. While it doesn't delete data permanently (Destructive), it forcibly terminates running processes, which can have significant side effects like incomplete data pipelines, partial writes, or downstream failures. This falls under Execute as it triggers an external operation affecting running processes.

From the tool's definition Cancel running jobs/scenarios

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cancel_running_jobs Rate-limited

cancel_running_jobs 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": {
    "cancel_running_jobs": {
      "limits": [
        {
          "counter": "cancel_running_jobs_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 Dataiku DSS MCP Server, so you can run agents against it safely.

FAQ

Questions about cancel_running_jobs

What does the cancel_running_jobs tool do? +

Cancel running jobs/scenarios. It is categorised as a Execute tool in the Dataiku DSS 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 cancel_running_jobs? +

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

What risk level is cancel_running_jobs? +

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

Can I rate-limit cancel_running_jobs? +

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

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

cancel_running_jobs is provided by the Dataiku DSS MCP Server MCP server (steven0lisa/mcp-dataiku). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.