New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_staking_rewards

Estimate staking rewards earned over a given period (7d/30d/90d/1y) using the current APR as a proxy. This is an estimate, not an on-chain rewards query.

SERVERVaultPilot MCP SOURCEvaultpilot-mcp
Low RISK CLASS
Category Read
Parameters 21 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-staking-rewards.md

What get_staking_rewards does on VaultPilot MCP

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

ParameterTypeRequiredDescription
period string Lookback window for aggregating accrued rewards. Defaults to 30d.
wallet string Yes 0x-prefixed EVM wallet address (40 hex chars) to inspect.

Parameters from the server's own tool schema.

Why get_staking_rewards is rated Low

The tool retrieves or calculates estimated staking rewards based on input parameters (period, current APR). It does not modify, delete, execute external operations, or commit financial transactions—it only reads/computes data for informational purposes. The explicit disclaimer that this is an estimate, not a live query, confirms it is a passive read operation.

From the tool's definition Tool name 'get_staking_rewards' and description explicitly state it 'estimate[s]' rewards 'using the current APR as a proxy' and is 'not an on-chain rewards query.' This is a calculation/retrieval operation with no side effects.

Questions about get_staking_rewards

What does the get_staking_rewards tool do? +

Estimate staking rewards earned over a given period (7d/30d/90d/1y) using the current APR as a proxy. This is an estimate, not an on-chain rewards query. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.

What parameters does get_staking_rewards accept? +

get_staking_rewards accepts 2 parameters: period, wallet. Required: wallet. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_staking_rewards? +

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

What risk level is get_staking_rewards? +

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

Can I rate-limit get_staking_rewards? +

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

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

get_staking_rewards is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on VaultPilot, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of VaultPilot's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.