get_reward_status

Get comprehensive reward status for an account including opt-in status,

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-reward-status.md

WHAT IT DOES

What get_reward_status does on Tempo

AI agents call get_reward_status 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_reward_status is rated Low

This tool queries account information (reward status, opt-in status) without creating, modifying, or deleting data. It is a read-only operation that retrieves existing state. Despite the server's broader capability for executing payments, this specific tool poses minimal risk as it only exposes informational queries about rewards.

From the tool's definition Tool name 'get_reward_status' and description 'Get comprehensive reward status for an account including opt-in status' indicate data retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_reward_status Allowed

get_reward_status 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_reward_status": {}
  }
}

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_reward_status call is checked against it from then on.

FAQ

Questions about get_reward_status

What does the get_reward_status tool do? +

Get comprehensive reward status for an account including opt-in status,. 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_reward_status? +

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

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

Can I rate-limit get_reward_status? +

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

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

get_reward_status 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_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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