get_cdps_by_owner
Get all CDPs/loans for a specific owner (accepts payment key hash or bech32 address)
This record as markdown: /tools/indigoprotocol-indigo-mcp/get-cdps-by-owner.md
What get_cdps_by_owner does on Indigo Protocol MCP
AI agents call get_cdps_by_owner 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 |
|---|---|---|---|
owner | string | — | Owner payment key hash (56-char hex) or bech32 address |
Parameters from the server's own tool schema.
Why get_cdps_by_owner is rated Low
The tool queries existing CDP (Collateralized Debt Position) data associated with an owner's address. This is a read operation that retrieves information without modifying, deleting, or executing any state changes. No financial transactions or code execution are involved.
From the tool's definition Tool retrieves CDP/loan data for a specific owner by querying their address; name and description indicate a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_cdps_by_owner 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_owner, this is the rule to start with:
get_cdps_by_owner 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_owner call is checked against it from then on.
Questions about get_cdps_by_owner
Get all CDPs/loans for a specific owner (accepts payment key hash or bech32 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_owner accepts 1 parameter: owner. 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_owner: 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_owner 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_owner 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_owner. 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_owner 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