annul_sp_request
Cancel a pending stability pool request. Returns an unsigned transaction (CBOR hex) for client-side signing.
This record as markdown: /tools/indigoprotocol-indigo-mcp/annul-sp-request.md
What annul_sp_request does on Indigo Protocol MCP
AI agents call annul_sp_request to permanently remove resources in Indigo Protocol MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
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 annul_sp_request is rated Critical
Cancelling a pending stability pool request is an irreversible action that terminates an in-flight financial operation on-chain. While it returns an unsigned transaction (requiring client signing), the intent is to permanently cancel/annul a request. This falls under Destructive as the cancellation of the pending request cannot be undone once submitted.
From the tool's definition Cancel a pending stability pool request
Attacks that exploit this kind of access
The rule that runs annul_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 annul_sp_request, this is the rule to start with:
annul_sp_request is removed from the agent's tool list entirely, so the agent never calls 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 annul_sp_request call is checked against it from then on.
Questions about annul_sp_request
Cancel a pending stability pool request. Returns an unsigned transaction (CBOR hex) for client-side signing. It is categorised as a Destructive tool in the Indigo Protocol MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
annul_sp_request 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 annul_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.
annul_sp_request is a Destructive 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 annul_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 annul_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.
annul_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