get_all_cdps
Get all CDPs/loans, optionally filtered by iAsset
This record as markdown: /tools/indigoprotocol-indigo-mcp/get-all-cdps.md
What get_all_cdps does on Indigo Protocol MCP
AI agents call get_all_cdps 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 |
|---|---|---|---|
asset | string | — | |
limit | number | — | |
offset | number | — |
Parameters from the server's own tool schema.
Why get_all_cdps is rated Low
This tool retrieves CDP (Collateralized Debt Position) and loan data without modifying, deleting, or executing any state-changing operations. It performs a read-only query against Indigo Protocol data. The blast radius of misuse is minimal—an agent could retrieve financial data but cannot move funds or alter positions.
From the tool's definition Tool name 'get_all_cdps' and description 'Get all CDPs/loans, optionally filtered by iAsset' indicate a retrieval operation with no side effects. The verb 'Get' combined with 'optionally filtered' confirms this is a query/fetch operation.
Attacks that exploit this kind of access
The rule that runs get_all_cdps 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_all_cdps, this is the rule to start with:
get_all_cdps 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_all_cdps call is checked against it from then on.
Questions about get_all_cdps
Get all CDPs/loans, optionally filtered by iAsset. It is categorised as a Read tool in the Indigo Protocol MCP MCP Server, which means it retrieves data without modifying state.
get_all_cdps accepts 3 parameters: asset, limit, offset. 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_all_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.
get_all_cdps 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_all_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.
Set action: deny in the PolicyLayer policy for get_all_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.
get_all_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.
This server
Across the catalogue