close_sp_account
Close a stability pool account and withdraw all deposited iAssets. Returns an unsigned transaction (CBOR hex) for client-side signing.
This record as markdown: /tools/indigoprotocol-indigo-mcp/close-sp-account.md
What close_sp_account does on Indigo Protocol MCP
AI agents use close_sp_account to create or update resources in Indigo Protocol MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Indigo Protocol MCP environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string | — | User Cardano bech32 address |
accountTxHash | string | — | Transaction hash of the account UTxO |
accountOutputIndex | number | — | Output index of the account UTxO |
Parameters from the server's own tool schema.
Why close_sp_account is rated Medium
This tool creates a reversible state change (closes account and withdraws funds) but the account can be reopened and funds can be redeposited, making it Write rather than Destructive. Severity is high because it moves user assets and affects account state, but the transaction must be signed by the client before execution, limiting immediate blast radius from agent misuse.
From the tool's definition Tool closes an account ('Close a stability pool account') and withdraws deposited iAssets ('withdraw all deposited iAssets'). It returns an unsigned transaction, indicating the action modifies blockchain state but does not execute autonomously.
Attacks that exploit this kind of access
The rule that runs close_sp_account 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 close_sp_account, this is the rule to start with:
close_sp_account stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 close_sp_account call is checked against it from then on.
Questions about close_sp_account
Close a stability pool account and withdraw all deposited iAssets. Returns an unsigned transaction (CBOR hex) for client-side signing. It is categorised as a Write tool in the Indigo Protocol MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
close_sp_account accepts 3 parameters: 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 close_sp_account: 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.
close_sp_account is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the close_sp_account 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 close_sp_account. 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.
close_sp_account 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.
This server
Across the catalogue