redeem_lrp
Redeem iAssets against one or more LRP positions. Returns an unsigned transaction (CBOR hex) for client-side signing.
This record as markdown: /tools/indigoprotocol-indigo-mcp/redeem-lrp.md
What redeem_lrp does on Indigo Protocol MCP
AI agents use redeem_lrp 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 |
iassetTxHash | string | — | Transaction hash of the iAsset UTxO |
redemptionLrps | array | — | Array of LRP positions and amounts to redeem against |
iassetOutputIndex | number | — | Output index of the iAsset UTxO |
priceOracleTxHash | string | — | Transaction hash of the price oracle UTxO |
priceOracleOutputIndex | number | — | Output index of the price oracle UTxO |
Parameters from the server's own tool schema.
Why redeem_lrp is rated Critical
This tool constructs a financial transaction that redeems iAssets (synthetic/tokenized financial instruments) against LRP positions on the Indigo Protocol DeFi platform. Redeeming assets is a financial operation that commits to exchanging or liquidating tokenized assets, which constitutes moving financial value. The transaction, once signed and submitted, irreversibly alters on-chain financial positions.
From the tool's definition Redeem iAssets against one or more LRP positions. Returns an unsigned transaction (CBOR hex) for client-side signing.
Attacks that exploit this kind of access
The rule that runs redeem_lrp 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 redeem_lrp, this is the rule to start with:
Any call to redeem_lrp 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 redeem_lrp call is checked against it from then on.
Questions about redeem_lrp
Redeem iAssets against one or more LRP positions. 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.
redeem_lrp accepts 6 parameters: address, iassetTxHash, redemptionLrps, iassetOutputIndex, priceOracleTxHash, priceOracleOutputIndex. 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 redeem_lrp: 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.
redeem_lrp 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 redeem_lrp 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 redeem_lrp. 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.
redeem_lrp 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