List BTC delegations for a finality provider.
AI agents call babylon_list_delegations to retrieve information from Tenzro Ledger MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The verb 'list' and the read-only nature of querying delegation data confirms this is a Read operation. There is no creation, modification, deletion, or execution of external operations. The blast radius if misused is minimal—an agent could only retrieve potentially sensitive delegation information, not alter blockchain state or move funds.
From the tool's definition Tool name 'babylon_list_delegations' and description 'List BTC delegations for a finality provider' both indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List BTC delegations for a finality provider. It is categorised as a Read tool in the Tenzro Ledger MCP MCP Server, which means it retrieves data without modifying state.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for babylon_list_delegations: 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 Tenzro Ledger MCP. Nothing to install.
babylon_list_delegations 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 babylon_list_delegations 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 babylon_list_delegations. 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.
babylon_list_delegations is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →