Claim all pending rewards for a TIP-20 token. Rewards are sent to your wallet
AI agents use claim_rewards to commit financial operations through Tempo — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Claiming rewards initiates a real-world financial transaction that moves token assets into a wallet. Given this is on a stablecoin payments platform designed for autonomous financial operations, this constitutes a financial action with high blast radius if misused (e.g., draining reward pools or claiming rewards not belonging to the agent).
From the tool's definition 'Claim all pending rewards for a TIP-20 token. Rewards are sent to your wallet' — this triggers a financial transfer of reward tokens to a wallet.
Documented attack patterns abuse exactly the kind of access claim_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 claim_rewards:
{
"version": "1",
"default": "deny",
"tools": {
"claim_rewards": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to claim_rewards is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Claim all pending rewards for a TIP-20 token. Rewards are sent to your wallet. 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 claim_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.
claim_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 claim_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 claim_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.
claim_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.