Cancel a pending scheduled payment before it executes.
AI agents use cancel_scheduled_payment to commit financial operations through Tempo — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Cancelling a scheduled payment is a financial operation that directly affects payment workflows and financial obligations. While it prevents a payment from executing (rather than moving money), it has direct financial consequences by stopping committed payment flows.
From the tool's definition cancel a pending scheduled payment before it executes
Documented attack patterns abuse exactly the kind of access cancel_scheduled_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 cancel_scheduled_payment:
{
"version": "1",
"default": "deny",
"tools": {
"cancel_scheduled_payment": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to cancel_scheduled_payment is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Cancel a pending scheduled payment before it executes. 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 cancel_scheduled_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.
cancel_scheduled_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 cancel_scheduled_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 cancel_scheduled_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.
cancel_scheduled_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.