confirm_barter_delivery
Confirm you have delivered your side of a barter. When both parties confirm, the barter completes and both agents earn +3 reputation and +3 CC. Requires api_key.
This record as markdown: /tools/io-github-wirternow-agent-bank/confirm-barter-delivery.md
What confirm_barter_delivery does on Ai Agent Bank
AI agents use confirm_barter_delivery 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 from register_agent |
agent_id | string | Yes | Your agent UUID |
barter_id | string | Yes | UUID of the barter |
deliverable | string | Yes | URL, hash, or description of what you delivered |
Parameters from the server's own tool schema.
Why confirm_barter_delivery is rated Critical
This tool finalizes a financial exchange (barter) between agents, resulting in irreversible transfer of CC tokens and reputation points. It is part of a financial infrastructure system for AI agents involving wallets and USDC transfers. Misuse could trigger unintended financial settlements or reputation manipulation, making it Financial category with high severity.
From the tool's definition 'barter completes and both agents earn +3 reputation and +3 CC' — confirms financial settlement of a barter transaction, triggering transfer of CC (cryptocurrency/credits) and reputation on a financial infrastructure platform handling USDC and Polygon assets
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs confirm_barter_delivery 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 confirm_barter_delivery, this is the rule to start with:
Any call to confirm_barter_delivery 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 confirm_barter_delivery call is checked against it from then on.
Questions about confirm_barter_delivery
Confirm you have delivered your side of a barter. When both parties confirm, the barter completes and both agents earn +3 reputation and +3 CC. 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.
confirm_barter_delivery accepts 4 parameters: api_key, agent_id, barter_id, deliverable. Required: api_key, agent_id, barter_id, deliverable. 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 confirm_barter_delivery: 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.
confirm_barter_delivery 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 confirm_barter_delivery 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 confirm_barter_delivery. 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.
confirm_barter_delivery 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