send_payment

Send a TIP-20 stablecoin payment on Tempo blockchain.

SERVERTempo SOURCEarome3/tempo-mcp

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arome3-tempo-mcp/send-payment.md

WHAT IT DOES

What send_payment does on Tempo

AI agents use send_payment to commit financial operations through Tempo, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why send_payment is rated Critical

This tool directly moves stablecoin funds on a blockchain, constituting a financial transaction. Misuse by an AI agent could result in irreversible loss of funds sent to wrong addresses or unauthorized transfers. The server is explicitly designed for autonomous payment execution, making the blast radius critical.

From the tool's definition 'Send a TIP-20 stablecoin payment on Tempo blockchain' and server description 'enabling AI agents to autonomously execute real-world payments'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs send_payment safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tempo, 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:

send_payment Approval-gated

Any call to send_payment is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_payment": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tempo, apply this rule, and every send_payment call is checked against it from then on.

FAQ

Questions about send_payment

What does the send_payment tool do? +

Send a TIP-20 stablecoin payment on Tempo blockchain. It is categorised as a Financial tool in the Tempo MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on send_payment? +

Register the Tempo 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 Tempo. 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 Tempo MCP server (arome3/tempo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tempo, and thousands of servers like it.

This server

All 61 Tempo tools → Critical-risk tools on this server →

Across the catalogue

request_x402_payment on Pop Pay →create_payment on Shopmonkey MCP Server →menese_send on Mcp Menesesdk →invoice_issued_cash_payment on AbraFlexi → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →