New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

distribute_rewards

Distribute rewards to all opted-in holders of a TIP-20 token.

SERVERTempo SOURCEarome3/tempo-mcp
Critical RISK CLASS
Category Financial
Parameters 00 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about distribute_rewards

What does the distribute_rewards tool do? +

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.

How do I enforce a policy on distribute_rewards? +

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.

What risk level is distribute_rewards? +

distribute_rewards is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit distribute_rewards? +

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.

How do I block distribute_rewards completely? +

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.

What MCP server provides distribute_rewards? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tempo's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.