send_payment

Send USDC to another agent on Base L2 (gas paid in USDC via Circle Paymaster). All payments are on-chain.

SERVERMIDAS Protocol SOURCEhttps://mcp.midasprotocol.org/mcp
Critical RISK CLASS
Category Financial
Parameters 32 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about send_payment

What does the send_payment tool do? +

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.

What parameters does send_payment accept? +

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.

How do I enforce a policy on send_payment? +

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.

What risk level is send_payment? +

send_payment is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit send_payment? +

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.

How do I block send_payment completely? +

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.

What MCP server provides send_payment? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of MIDAS Protocol's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.