distribute_rewards
Distribute rewards to all opted-in holders of a TIP-20 token.
This record as markdown: /tools/arome3-tempo-mcp/distribute-rewards.md
What distribute_rewards does on Tempo
AI agents use distribute_rewards to commit financial operations through Tempo, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why distribute_rewards is rated Critical
This tool executes a financial operation that distributes token rewards to holders on the Tempo blockchain. Given the server's purpose of executing real-world stablecoin payments, distributing rewards constitutes committing financial obligations and moving monetary value at scale to multiple recipients, making it Financial category with critical severity due to the potential blast radius of a mass payout operation…
From the tool's definition 'Distribute rewards to all opted-in holders of a TIP-20 token' — this moves financial value (rewards/payments) to multiple recipients on a blockchain
Attacks that exploit this kind of access
The rule that runs distribute_rewards 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 distribute_rewards, this is the rule to start with:
Any call to distribute_rewards 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 distribute_rewards call is checked against it from then on.
Questions about distribute_rewards
Distribute rewards to all opted-in holders of a TIP-20 token. 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 distribute_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.
distribute_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 distribute_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 distribute_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.
distribute_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.
More on Tempo, and thousands of servers like it.
Across the catalogue