Send a TIP-20 payment with gas fees paid by a sponsor (gasless transaction).
AI agents use send_sponsored_payment to commit financial operations through Tempo — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool executes a blockchain payment transaction, transferring stablecoin value on the Tempo blockchain. It directly moves financial assets between parties, which qualifies as Financial — the highest severity category. The 'gasless' aspect means an AI agent could trigger real-world payments without even needing gas funds, lowering the barrier to misuse.
From the tool's definition Send a TIP-20 payment with gas fees paid by a sponsor (gasless transaction)
Documented attack patterns abuse exactly the kind of access send_sponsored_payment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tempo, and nothing reaches the server without passing your rules. This is the rule we recommend for send_sponsored_payment:
{
"version": "1",
"default": "deny",
"tools": {
"send_sponsored_payment": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to send_sponsored_payment is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Send a TIP-20 payment with gas fees paid by a sponsor (gasless transaction). 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.
Register the Tempo MCP server in PolicyLayer and add a rule for send_sponsored_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.
send_sponsored_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_sponsored_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_sponsored_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_sponsored_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.
Start from Tempo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
61 Tempo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.