schedule_payment
Create a scheduled payment that executes at a future time on Tempo blockchain.
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
Attacks that exploit this kind of access
The rule that runs schedule_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 schedule_payment, this is the rule to start with:
Any call to schedule_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 Tempo, apply this rule, and every schedule_payment call is checked against it from then on.
Questions about schedule_payment
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.
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.
schedule_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 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.
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.
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.
Across the catalogue