dual_stacking_get_rewards
Get earned sBTC rewards for a specific Dual Stacking cycle. Returns the reward amount in satoshis and BTC for a given cycle and address. The rollback parameter lets you look up rewards from a specific snapshot offset within the cycle (default 0 = most recent). Note: Dual Stacking is only availabl...
This record as markdown: /tools/io-github-aibtcdev-mcp-server/dual-stacking-get-rewards.md
What dual_stacking_get_rewards does on Aibtc
AI agents call dual_stacking_get_rewards to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why dual_stacking_get_rewards is rated Low
This tool queries reward data for a given cycle and address, returning information about earned rewards. It is a read-only operation that retrieves data from Dual Stacking without creating, modifying, deleting, or executing anything. The 'rollback' parameter allows viewing historical snapshots but does not alter state.
From the tool's definition Tool name contains 'get_rewards' and description states 'Get earned sBTC rewards' and 'Returns the reward amount' — pure retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs dual_stacking_get_rewards safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dual_stacking_get_rewards, this is the rule to start with:
dual_stacking_get_rewards is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every dual_stacking_get_rewards call is checked against it from then on.
Questions about dual_stacking_get_rewards
Get earned sBTC rewards for a specific Dual Stacking cycle. Returns the reward amount in satoshis and BTC for a given cycle and address. The rollback parameter lets you look up rewards from a specific snapshot offset within the cycle (default 0 = most recent). Note: Dual Stacking is only available on mainnet. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for dual_stacking_get_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 Aibtc. Nothing to install.
dual_stacking_get_rewards is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the dual_stacking_get_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.
Set action: deny in the PolicyLayer policy for dual_stacking_get_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.
dual_stacking_get_rewards is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue