transfer_cc
Send Capability Credits to another agent. Use for direct payments, tips, or splitting earnings. No blockchain transaction needed — instant settlement. Requires api_key.
This record as markdown: /tools/io-github-wirternow-agent-bank/transfer-cc.md
What transfer_cc does on Ai Agent Bank
AI agents use transfer_cc to commit financial operations through Ai Agent Bank, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
note | string | — | Optional note for the transfer |
amount | number | Yes | Amount in COGS to transfer (integer). 10,000 cogs = 1 CC. Minimum: 1000 cogs. |
api_key | string | Yes | Your api_key from register_agent |
to_agent_id | string | Yes | Recipient agent UUID |
from_agent_id | string | Yes | Your agent UUID |
Parameters from the server's own tool schema.
Why transfer_cc is rated Critical
This tool commits financial obligations by transferring credits/value between accounts. It directly moves monetary assets (Capability Credits), which is the defining characteristic of the Financial category.
From the tool's definition Tool description explicitly states 'Send Capability Credits to another agent' and 'direct payments', combined with server description 'Financial infrastructure for AI agents: wallets, USDC transfers'. The tool moves value between accounts.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs transfer_cc safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ai Agent Bank, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transfer_cc, this is the rule to start with:
Any call to transfer_cc is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ai Agent Bank, apply this rule, and every transfer_cc call is checked against it from then on.
Questions about transfer_cc
Send Capability Credits to another agent. Use for direct payments, tips, or splitting earnings. No blockchain transaction needed — instant settlement. Requires api_key. It is categorised as a Financial tool in the Ai Agent Bank MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
transfer_cc accepts 5 parameters: note, amount, api_key, to_agent_id, from_agent_id. Required: amount, api_key, to_agent_id, from_agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the Ai Agent Bank MCP server in PolicyLayer and add a rule for transfer_cc: 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 Ai Agent Bank. Nothing to install.
transfer_cc 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 transfer_cc 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 transfer_cc. 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.
transfer_cc is provided by the Ai Agent Bank MCP server (https://tdueqhfxyojmjgactdyc.supabase.co/functions/v1/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ai Agent Bank, and thousands of servers like it.
Across the catalogue