cancel_prediction

Cancel a running prediction

SERVERReplicate MCP Server SOURCEdeepfates/mcp-replicate

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/deepfates-mcp-replicate/cancel-prediction.md

WHAT IT DOES

What cancel_prediction does on Replicate MCP Server

AI agents invoke cancel_prediction to trigger actions in Replicate 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 cancel_prediction is rated High

Cancelling a running prediction is an external operation that terminates an in-progress computation on Replicate's infrastructure. It is not purely destructive (no data is permanently deleted) nor a simple read/write, but it triggers an irreversible state change on an external running process.

From the tool's definition Cancel a running prediction

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cancel_prediction safely

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

cancel_prediction Rate-limited

cancel_prediction 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_prediction": {
      "limits": [
        {
          "counter": "cancel_prediction_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 Replicate MCP Server, apply this rule, and every cancel_prediction call is checked against it from then on.

FAQ

Questions about cancel_prediction

What does the cancel_prediction tool do? +

Cancel a running prediction. It is categorised as a Execute tool in the Replicate 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_prediction? +

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

What risk level is cancel_prediction? +

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

Can I rate-limit cancel_prediction? +

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

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

cancel_prediction is provided by the Replicate MCP Server MCP server (deepfates/mcp-replicate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 13 Replicate 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 →