merge_cdps

Merge multiple CDPs into one — builds an unsigned transaction (CBOR hex) for client-side signing

SERVERIndigo Protocol MCP SOURCEindigoprotocol/indigo-mcp
Medium RISK CLASS
Category Write
Parameters 20 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/indigoprotocol-indigo-mcp/merge-cdps.md

What merge_cdps does on Indigo Protocol MCP

AI agents use merge_cdps 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.

ParameterTypeRequiredDescription
address string User Cardano bech32 address (addr1... or addr_test1...)
cdpOutRefs array Array of CDP UTxO references to merge (minimum 2)

Parameters from the server's own tool schema.

Why merge_cdps is rated Medium

This tool merges multiple Collateralized Debt Positions (CDPs) into one by constructing an unsigned transaction. While it doesn't execute the transaction directly (client-side signing required), it restructures financial positions on a DeFi protocol, which constitutes a significant Write operation affecting collateral and debt positions.

From the tool's definition Merge multiple CDPs into one — builds an unsigned transaction (CBOR hex) for client-side signing

Questions about merge_cdps

What does the merge_cdps tool do? +

Merge multiple CDPs into one — builds 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.

What parameters does merge_cdps accept? +

merge_cdps accepts 2 parameters: address, cdpOutRefs. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on merge_cdps? +

Register the Indigo Protocol MCP server in PolicyLayer and add a rule for merge_cdps: 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.

What risk level is merge_cdps? +

merge_cdps is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit merge_cdps? +

Yes. Add a rate_limit block to the merge_cdps 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.

How do I block merge_cdps completely? +

Set action: deny in the PolicyLayer policy for merge_cdps. 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.

What MCP server provides merge_cdps? +

merge_cdps 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Indigo Protocol's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.