withdraw_cc
Withdraw Capability Credits from the platform to your Polygon wallet address. Debits your internal CC balance and executes an ERC-20 transfer on Polygon mainnet. Minimum 1 CC (10,000 cogs). Returns tx_hash and Polygonscan link.
This record as markdown: /tools/io-github-wirternow-agent-bank/withdraw-cc.md
What withdraw_cc does on Ai Agent Bank
AI agents use withdraw_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 |
|---|---|---|---|
api_key | string | Yes | Your api_key |
agent_id | string | Yes | Your agent UUID |
to_address | string | — | Polygon wallet address to send to (optional — defaults to your registered wallet) |
cogs_amount | number | Yes | Amount to withdraw in cogs (10,000 = 1 CC) |
Parameters from the server's own tool schema.
Why withdraw_cc is rated Critical
This tool directly moves financial assets (Capability Credits denominated in cogs) from an internal platform balance to a user's blockchain wallet, executing an irreversible ERC-20 transfer on Polygon. This is a classic financial transaction that commits monetary value.
From the tool's definition Withdraw Capability Credits from the platform to your Polygon wallet address. Debits your internal CC balance and executes an ERC-20 transfer on Polygon mainnet.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs withdraw_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 withdraw_cc, this is the rule to start with:
Any call to withdraw_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 withdraw_cc call is checked against it from then on.
Questions about withdraw_cc
Withdraw Capability Credits from the platform to your Polygon wallet address. Debits your internal CC balance and executes an ERC-20 transfer on Polygon mainnet. Minimum 1 CC (10,000 cogs). Returns tx_hash and Polygonscan link. 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.
withdraw_cc accepts 4 parameters: api_key, agent_id, to_address, cogs_amount. Required: api_key, agent_id, cogs_amount. 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 withdraw_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.
withdraw_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 withdraw_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 withdraw_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.
withdraw_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