AI agents use accept_project_transfer to commit financial operations through Run402 — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly handles wallet transfers, which are financial transactions. Misuse by an AI agent could result in unauthorized fund transfers. The fact that it requires wallet validation suggests it's part of a payment/billing system. Financial transactions are the most severe category and take precedence over other risk types.
From the tool's definition Tool explicitly performs a 'WALLET transfer' acceptance. The description states it accepts an incoming transfer and requires wallet equality, indicating it commits financial obligations and moves money between accounts.
Attacks that exploit this kind of access
Accept an incoming WALLET transfer (v1.93+). Your wallet must equal the transfer. It is categorised as a Financial tool in the Run402 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Run402 MCP server in PolicyLayer and add a rule for accept_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.
accept_project_transfer is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the accept_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.
Set action: deny in the PolicyLayer policy for accept_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.
accept_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →