New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

schedule_payment

Create a scheduled payment that executes at a future time 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/schedule-payment.md

What schedule_payment does on Tempo

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

Why schedule_payment is rated Critical

This tool schedules a future payment on the Tempo blockchain stablecoin network. It directly commits financial obligations that will execute autonomously at a future time. Even though it may be cancellable (given the sibling 'cancel_scheduled_payment' tool exists), the act of scheduling constitutes a financial commitment.

From the tool's definition 'Create a scheduled payment that executes at a future time on Tempo blockchain' — explicitly commits a financial payment obligation on the blockchain

Questions about schedule_payment

What does the schedule_payment tool do? +

Create a scheduled payment that executes at a future time 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 schedule_payment? +

Register the Tempo MCP server in PolicyLayer and add a rule for schedule_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 schedule_payment? +

schedule_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 schedule_payment? +

Yes. Add a rate_limit block to the schedule_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 schedule_payment completely? +

Set action: deny in the PolicyLayer policy for schedule_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 schedule_payment? +

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

More on Tempo, 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 Tempo'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.