process_sp_request
Process a pending stability pool request (protocol maintenance operation). Returns an unsigned transaction (CBOR hex) for client-side signing.
This record as markdown: /tools/indigoprotocol-indigo-mcp/process-sp-request.md
What process_sp_request does on Indigo Protocol MCP
AI agents invoke process_sp_request to trigger actions in Indigo Protocol MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
asset | string | — | iAsset of the stability pool (iUSD, iBTC, iETH, or iSOL) |
address | string | — | User Cardano bech32 address |
accountTxHash | string | — | Transaction hash of the account UTxO with the pending request |
accountOutputIndex | number | — | Output index of the account UTxO |
Parameters from the server's own tool schema.
Why process_sp_request is rated High
This tool triggers an on-chain protocol operation by constructing a transaction that interacts with the Indigo Protocol's stability pool. While it returns an unsigned transaction (requiring client-side signing), it initiates a financial protocol action. The sibling tools context (adjust_sp_account, close_sp_account, etc.) suggests this involves real DeFi/financial positions.
From the tool's definition Process a pending stability pool request (protocol maintenance operation). Returns an unsigned transaction (CBOR hex) for client-side signing.
Attacks that exploit this kind of access
The rule that runs process_sp_request 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 process_sp_request, this is the rule to start with:
process_sp_request stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Indigo Protocol MCP, apply this rule, and every process_sp_request call is checked against it from then on.
Questions about process_sp_request
Process a pending stability pool request (protocol maintenance operation). Returns an unsigned transaction (CBOR hex) for client-side signing. It is categorised as a Execute tool in the Indigo Protocol MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
process_sp_request accepts 4 parameters: asset, address, accountTxHash, accountOutputIndex. 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 process_sp_request: 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.
process_sp_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the process_sp_request 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 process_sp_request. 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.
process_sp_request 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