Low Risk

get_pending_rewards

Check the pending reward balance for an address. Returns the amount of

How to control get_pending_rewards ↓

What get_pending_rewards does on Tempo

AI agents call get_pending_rewards to retrieve information from Tempo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_pending_rewards needs a policy

This tool retrieves information about pending rewards without modifying, executing, or deleting any data. It is a read-only query operation that simply returns a balance amount for an address. Despite being on a financial blockchain system, the tool itself performs no financial transactions—it only reads state.

From the tool's definition Tool name 'get_pending_rewards' and description 'Check the pending reward balance for an address' indicate a query/retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_pending_rewards gives an agent:

How to control get_pending_rewards

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 get_pending_rewards:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_pending_rewards": {}
  }
}

get_pending_rewards is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Tempo — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_pending_rewards

What does the get_pending_rewards tool do? +

Check the pending reward balance for an address. Returns the amount of. It is categorised as a Read tool in the Tempo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pending_rewards? +

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

get_pending_rewards is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_pending_rewards? +

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

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

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

Enforce policy on every Tempo tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.