Opt out of rewards for a TIP-20 token. By default, any pending rewards will be
AI agents use opt_out_rewards to commit financial operations through Tempo — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Opting out of rewards on a financial blockchain protocol constitutes a financial action that forfeits or waives pending monetary rewards. On a stablecoin/payment blockchain (Tempo), rewards represent real financial value. Misuse could cause an AI agent to irreversibly forfeit accumulated rewards on behalf of a user.
From the tool's definition 'Opt out of rewards for a TIP-20 token' and 'any pending rewards will be' (description appears truncated) — this action affects financial reward claims on a stablecoin payments blockchain
Documented attack patterns abuse exactly the kind of access opt_out_rewards 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 opt_out_rewards:
{
"version": "1",
"default": "deny",
"tools": {
"opt_out_rewards": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to opt_out_rewards is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Opt out of rewards for a TIP-20 token. By default, any pending rewards will be. 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 opt_out_rewards: 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.
opt_out_rewards 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 opt_out_rewards 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 opt_out_rewards. 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.
opt_out_rewards 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.