get_pending_rewards

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

SERVERTempo SOURCEarome3/tempo-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arome3-tempo-mcp/get-pending-rewards.md

WHAT IT DOES

What get_pending_rewards does on Tempo

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

RISK

Why get_pending_rewards is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_pending_rewards Allowed

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_pending_rewards": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

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.

KEEP EXPLORING

More on Tempo, and thousands of servers like it.

This server

All 61 Tempo tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →