send_payment
Send USDC to another agent on Base L2 (gas paid in USDC via Circle Paymaster). All payments are on-chain.
This record as markdown: /tools/io-github-bbrainfrance-midas-protocol/send-payment.md
What send_payment does on MIDAS Protocol
AI agents use send_payment to commit financial operations through MIDAS Protocol, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
amount | number | Yes | |
reason | string | — | |
toAgentId | string | Yes |
Parameters from the server's own tool schema.
Why send_payment is rated Critical
This tool directly moves financial assets (USDC stablecoin) on-chain. Misuse by an AI agent could result in irreversible loss of funds. On-chain transactions are permanent and cannot be reversed, making this both Financial and highly critical in blast radius.
From the tool's definition 'Send USDC to another agent on Base L2' and 'All payments are on-chain' — this tool transfers cryptocurrency (USDC) on a blockchain network.
Attacks that exploit this kind of access
The rule that runs send_payment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MIDAS Protocol, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_payment, this is the rule to start with:
Any call to send_payment is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect MIDAS Protocol, apply this rule, and every send_payment call is checked against it from then on.
Questions about send_payment
Send USDC to another agent on Base L2 (gas paid in USDC via Circle Paymaster). All payments are on-chain. It is categorised as a Financial tool in the MIDAS Protocol MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
send_payment accepts 3 parameters: amount, reason, toAgentId. Required: amount, toAgentId. The full parameter table on this page comes from the server's own tool schema.
Register the MIDAS Protocol MCP server in PolicyLayer and add a rule for send_payment: 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 MIDAS Protocol. Nothing to install.
send_payment 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 send_payment 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 send_payment. 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.
send_payment is provided by the MIDAS Protocol MCP server (https://mcp.midasprotocol.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MIDAS Protocol, and thousands of servers like it.
Across the catalogue