distribute_staking_rewards
Distribute collected ADA rewards from collector UTxOs to staking positions. This is a protocol maintenance operation that anyone can call. Returns an unsigned transaction (CBOR hex) for client-side signing.
This record as markdown: /tools/indigoprotocol-indigo-mcp/distribute-staking-rewards.md
What distribute_staking_rewards does on Indigo Protocol MCP
AI agents use distribute_staking_rewards to commit financial operations through Indigo Protocol MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string | — | User Cardano bech32 address |
collectorTxHashes | array | — | Array of collector UTxO references to distribute rewards from |
Parameters from the server's own tool schema.
Why distribute_staking_rewards is rated Critical
This tool distributes ADA rewards (real cryptocurrency) from protocol collector UTxOs to staking positions. Moving/distributing cryptocurrency assets constitutes a financial operation. While described as a maintenance operation open to anyone, it triggers on-chain movement of ADA funds.
From the tool's definition Distribute collected ADA rewards from collector UTxOs to staking positions... Returns an unsigned transaction (CBOR hex) for client-side signing.
Attacks that exploit this kind of access
The rule that runs distribute_staking_rewards safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Indigo Protocol MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For distribute_staking_rewards, this is the rule to start with:
Any call to distribute_staking_rewards is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Indigo Protocol MCP, apply this rule, and every distribute_staking_rewards call is checked against it from then on.
Questions about distribute_staking_rewards
Distribute collected ADA rewards from collector UTxOs to staking positions. This is a protocol maintenance operation that anyone can call. Returns an unsigned transaction (CBOR hex) for client-side signing. It is categorised as a Financial tool in the Indigo Protocol MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
distribute_staking_rewards accepts 2 parameters: address, collectorTxHashes. The full parameter table on this page comes from the server's own tool schema.
Register the Indigo Protocol MCP server in PolicyLayer and add a rule for distribute_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 Indigo Protocol MCP. Nothing to install.
distribute_staking_rewards is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the distribute_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.
Set action: deny in the PolicyLayer policy for distribute_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.
distribute_staking_rewards is provided by the Indigo Protocol MCP server (indigoprotocol/indigo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Indigo Protocol, and thousands of servers like it.
Across the catalogue