get_cdps_by_address

Get all CDPs/loans for a specific Cardano address

SERVERIndigo Protocol MCP SOURCEindigoprotocol/indigo-mcp
Low RISK CLASS
Category Read
Parameters 10 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/indigoprotocol-indigo-mcp/get-cdps-by-address.md

What get_cdps_by_address does on Indigo Protocol MCP

AI agents call get_cdps_by_address to retrieve information from Indigo Protocol MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
address string Cardano bech32 address (addr1... or addr_test1...)

Parameters from the server's own tool schema.

Why get_cdps_by_address is rated Low

This is a read-only query operation that retrieves existing Collateralized Debt Position (CDP) information associated with a blockchain address. It has no side effects, does not execute transactions, and does not modify data. While it accesses financial information, it is purely informational retrieval, making it a Read category tool with low severity risk.

From the tool's definition Tool name 'get_cdps_by_address' and description 'Get all CDPs/loans for a specific Cardano address' indicate retrieval of financial data without modification or execution of transactions.

Questions about get_cdps_by_address

What does the get_cdps_by_address tool do? +

Get all CDPs/loans for a specific Cardano address. It is categorised as a Read tool in the Indigo Protocol MCP MCP Server, which means it retrieves data without modifying state.

What parameters does get_cdps_by_address accept? +

get_cdps_by_address accepts 1 parameter: address. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_cdps_by_address? +

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

get_cdps_by_address is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_cdps_by_address? +

Yes. Add a rate_limit block to the get_cdps_by_address 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 get_cdps_by_address completely? +

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

get_cdps_by_address 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.

// 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.