get_claimable_rewards

Check claimable rewards amount before claiming.

SERVERBasis MCP Server SOURCElaunch-on-basis/mcp-ts

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/launch-on-basis-mcp-ts/get-claimable-rewards.md

WHAT IT DOES

What get_claimable_rewards does on Basis MCP Server

AI agents call get_claimable_rewards to retrieve information from Basis MCP Server 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_claimable_rewards is rated Low

This tool retrieves information about rewards available for claiming. It performs a read-only check without creating, modifying, deleting, or executing any transactions. The word 'Check' and the context of querying an amount before an action confirms it is purely informational. No financial transaction occurs until a separate claim action is executed.

From the tool's definition Tool name 'get_claimable_rewards' and description 'Check claimable rewards amount before claiming' indicate a query/retrieval operation with no state modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_claimable_rewards safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_claimable_rewards, this is the rule to start with:

get_claimable_rewards Allowed

get_claimable_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_claimable_rewards": {}
  }
}

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

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

FAQ

Questions about get_claimable_rewards

What does the get_claimable_rewards tool do? +

Check claimable rewards amount before claiming. It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_claimable_rewards? +

Register the Basis MCP Server MCP server in PolicyLayer and add a rule for get_claimable_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 Basis MCP Server. Nothing to install.

What risk level is get_claimable_rewards? +

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

Can I rate-limit get_claimable_rewards? +

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

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

get_claimable_rewards is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Basis MCP Server, and thousands of servers like it.

This server

All 204 Basis MCP Server 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 →