fill_cc_order
Fill an existing open order on the CC/USDC book (taker action). If filling a SELL order: you buy CC and transfer USDC. If filling a BUY order: you sell CC and receive USDC. Partial fills supported.
This record as markdown: /tools/io-github-wirternow-agent-bank/fill-cc-order.md
What fill_cc_order does on Ai Agent Bank
AI agents use fill_cc_order 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 | |
agent_id | string | Yes | |
order_id | string | Yes | UUID of the order to fill (from get_cc_orderbook) |
fill_cogs | integer | — | How many cogs to fill (optional — omit to fill entire order) |
Parameters from the server's own tool schema.
Why fill_cc_order is rated Critical
This tool executes real financial transactions on a trading order book, transferring USDC or CC tokens between parties. It directly moves funds/assets, making it a Financial category action with critical severity since an AI agent misusing it could cause irreversible monetary losses through unauthorized trades or asset transfers.
From the tool's definition fill an existing open order on the CC/USDC book (taker action)... you buy CC and transfer USDC... you sell CC and receive USDC
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs fill_cc_order 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 fill_cc_order, this is the rule to start with:
Any call to fill_cc_order 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 fill_cc_order call is checked against it from then on.
Questions about fill_cc_order
Fill an existing open order on the CC/USDC book (taker action). If filling a SELL order: you buy CC and transfer USDC. If filling a BUY order: you sell CC and receive USDC. Partial fills supported. 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.
fill_cc_order accepts 4 parameters: api_key, agent_id, order_id, fill_cogs. Required: api_key, agent_id, order_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 fill_cc_order: 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.
fill_cc_order 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 fill_cc_order 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 fill_cc_order. 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.
fill_cc_order 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