claim_project_transfer · Run402 MCP: Risk & Policy

WHAT IT DOES

What claim_project_transfer does on Run402

AI agents use claim_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 claim_project_transfer needs a policy

Claiming a project transfer modifies ownership/membership of a project, moving it into an organization. This is a reversible write operation (ownership can potentially be transferred back), but it has high blast radius as it changes control of an entire project. It is not destructive (no data is deleted), not financial (no money moves), but it is a significant organizational change.

From the tool's definition 'Claim an incoming EMAIL transfer into an org' — transfers project ownership into an organization

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

claim_project_transfer Rate-limited

claim_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": {
    "claim_project_transfer": {
      "limits": [
        {
          "counter": "claim_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 claim_project_transfer

What does the claim_project_transfer tool do? +

Claim an incoming EMAIL transfer into an org (v1.93+) — the email analog of. 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 claim_project_transfer? +

Register the Run402 MCP server in PolicyLayer and add a rule for claim_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 claim_project_transfer? +

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

Can I rate-limit claim_project_transfer? +

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

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

claim_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.