set_reward_recipient

Set or clear the auto-forward recipient for rewards. When a recipient is set,

SERVERTempo SOURCEarome3/tempo-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arome3-tempo-mcp/set-reward-recipient.md

WHAT IT DOES

What set_reward_recipient does on Tempo

AI agents use set_reward_recipient to create or update resources in Tempo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tempo environment.

RISK

Why set_reward_recipient is rated Medium

This tool creates or modifies a reward recipient configuration, which is a Write operation (reversible state change). However, severity is high rather than medium because: (1) it operates within a financial system (Tempo blockchain stablecoin payments), (2) misconfiguration could redirect rewards to unintended addresses, and (3) it affects autonomous payment flows where an AI agent error could cause financial losses.

From the tool's definition "Set or clear the auto-forward recipient for rewards" - modifies reward distribution configuration by setting or clearing a recipient address, which is a reversible change to payment routing logic.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_reward_recipient 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 set_reward_recipient, this is the rule to start with:

set_reward_recipient Rate-limited

set_reward_recipient stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_reward_recipient": {
      "limits": [
        {
          "counter": "set_reward_recipient_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tempo, apply this rule, and every set_reward_recipient call is checked against it from then on.

FAQ

Questions about set_reward_recipient

What does the set_reward_recipient tool do? +

Set or clear the auto-forward recipient for rewards. When a recipient is set,. It is categorised as a Write tool in the Tempo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_reward_recipient? +

Register the Tempo MCP server in PolicyLayer and add a rule for set_reward_recipient: 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 set_reward_recipient? +

set_reward_recipient is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_reward_recipient? +

Yes. Add a rate_limit block to the set_reward_recipient 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 set_reward_recipient completely? +

Set action: deny in the PolicyLayer policy for set_reward_recipient. 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 set_reward_recipient? +

set_reward_recipient 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.

KEEP EXPLORING

More on Tempo, and thousands of servers like it.

This server

All 61 Tempo tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →