cdp_rerun_job

Re-run a completed or failed workflow job

SERVERCDP MCP Server SOURCEatharva-joshi77/cdp-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/atharva-joshi77-cdp-mcp/cdp-rerun-job.md

WHAT IT DOES

What cdp_rerun_job does on CDP MCP Server

AI agents invoke cdp_rerun_job to trigger actions in CDP 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.

RISK

Why cdp_rerun_job is rated High

This tool executes an external operation (a workflow job) whose side effects depend on the job definition. While not inherently destructive, it can modify data or trigger integrations depending on what the workflow does. It is more severe than Write (reversible data creation/modification) because workflow jobs may have cascading effects beyond simple data updates.

From the tool's definition 'Re-run a completed or failed workflow job' - this triggers execution of a workflow job with effects that depend on the job's configuration and payload, which are not specified by this tool's arguments alone.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cdp_rerun_job safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CDP MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cdp_rerun_job, this is the rule to start with:

cdp_rerun_job Rate-limited

cdp_rerun_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": {
    "cdp_rerun_job": {
      "limits": [
        {
          "counter": "cdp_rerun_job_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CDP MCP Server, apply this rule, and every cdp_rerun_job call is checked against it from then on.

FAQ

Questions about cdp_rerun_job

What does the cdp_rerun_job tool do? +

Re-run a completed or failed workflow job. It is categorised as a Execute tool in the CDP 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 cdp_rerun_job? +

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

What risk level is cdp_rerun_job? +

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

Can I rate-limit cdp_rerun_job? +

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

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

cdp_rerun_job is provided by the CDP MCP Server MCP server (atharva-joshi77/cdp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CDP MCP Server, and thousands of servers like it.

This server

All 288 CDP MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →