cancel_project_transfer · Run402 MCP: Risk & Policy

WHAT IT DOES

What cancel_project_transfer does on Run402

AI agents use cancel_project_transfer to create or update resources in Run402 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Run402 environment.

WHY IT NEEDS A POLICY

Why cancel_project_transfer needs a policy

Cancelling a pending transfer modifies/revokes a pending action, which is a reversible write operation (the transfer can be re-initiated). It does not delete data irreversibly, execute code, or move money. Severity is medium because cancelling a transfer could disrupt legitimate ownership changes, but the blast radius is limited.

From the tool's definition Cancel a pending project transfer of any kind

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cancel_project_transfer Rate-limited

cancel_project_transfer stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_project_transfer": {
      "limits": [
        {
          "counter": "cancel_project_transfer_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Run402, so you can run agents against it safely.

FAQ

Questions about cancel_project_transfer

What does the cancel_project_transfer tool do? +

Cancel a pending project transfer of any kind (v1.93+). You must be authorized for the row. It is categorised as a Write tool in the Run402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cancel_project_transfer? +

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

What risk level is cancel_project_transfer? +

cancel_project_transfer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cancel_project_transfer? +

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

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

cancel_project_transfer is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

cancel_project_transfer is one line of Run402's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →