freeze_cdp
Freeze a CDP to prevent further operations until unfrozen — builds an unsigned transaction (CBOR hex) for client-side signing
This record as markdown: /tools/indigoprotocol-indigo-mcp/freeze-cdp.md
What freeze_cdp does on Indigo Protocol MCP
AI agents invoke freeze_cdp 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 | — | |
address | string | — | User Cardano bech32 address (addr1... or addr_test1...) |
cdpTxHash | string | — | Transaction hash of the CDP UTxO |
cdpOutputIndex | number | — | Output index of the CDP UTxO |
Parameters from the server's own tool schema.
Why freeze_cdp is rated High
This tool executes a blockchain transaction that freezes a Collateralized Debt Position (CDP), preventing further operations. While it builds an unsigned transaction (requiring client-side signing), the action itself triggers an external blockchain operation with significant consequences — locking a CDP and halting all associated financial operations.
From the tool's definition Freeze a CDP to prevent further operations until unfrozen — builds an unsigned transaction (CBOR hex) for client-side signing
Attacks that exploit this kind of access
The rule that runs freeze_cdp 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 freeze_cdp, this is the rule to start with:
freeze_cdp 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 freeze_cdp call is checked against it from then on.
Questions about freeze_cdp
Freeze a CDP to prevent further operations until unfrozen — builds 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.
freeze_cdp accepts 4 parameters: asset, address, cdpTxHash, cdpOutputIndex. 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 freeze_cdp: 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.
freeze_cdp 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 freeze_cdp 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 freeze_cdp. 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.
freeze_cdp 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