claim_lrp
Claim received iAssets from an LRP position. Returns an unsigned transaction (CBOR hex) for client-side signing.
This record as markdown: /tools/indigoprotocol-indigo-mcp/claim-lrp.md
What claim_lrp does on Indigo Protocol MCP
AI agents use claim_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 |
lrpTxHash | string | — | Transaction hash of the LRP UTxO |
lrpOutputIndex | number | — | Output index of the LRP UTxO |
Parameters from the server's own tool schema.
Why claim_lrp is rated Critical
This tool claims iAssets (synthetic assets) from a Liquidity Reserve Position on a DeFi protocol, which constitutes moving financial assets/tokens. The transaction involves claiming crypto assets, making it a Financial category action with high severity since misuse could result in unauthorized asset claims or loss of funds.
From the tool's definition Claim received iAssets from an LRP position. Returns an unsigned transaction (CBOR hex) for client-side signing.
Attacks that exploit this kind of access
The rule that runs claim_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 claim_lrp, this is the rule to start with:
Any call to claim_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 claim_lrp call is checked against it from then on.
Questions about claim_lrp
Claim received iAssets from an LRP position. 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.
claim_lrp accepts 3 parameters: address, lrpTxHash, lrpOutputIndex. 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 claim_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.
claim_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 claim_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 claim_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.
claim_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