get_cdps_by_address
Get all CDPs/loans for a specific Cardano address
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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.
Attacks that exploit this kind of access
The rule that runs get_cdps_by_address 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 get_cdps_by_address, this is the rule to start with:
get_cdps_by_address is read-only, so it stays allowed. 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 get_cdps_by_address call is checked against it from then on.
Questions about get_cdps_by_address
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.
get_cdps_by_address accepts 1 parameter: address. 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 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.
get_cdps_by_address is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
This server
Across the catalogue