babylon_list_delegations

List BTC delegations for a finality provider.

SERVERTenzro Ledger MCP SOURCEhttps://canton-mcp.tenzro.network/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/network-tenzro-tenzro/babylon-list-delegations.md

WHAT IT DOES

What babylon_list_delegations does on Tenzro Ledger MCP

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

RISK

Why babylon_list_delegations is rated Low

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

RECOMMENDED RULE

The rule that runs babylon_list_delegations safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For babylon_list_delegations, this is the rule to start with:

babylon_list_delegations Allowed

babylon_list_delegations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "babylon_list_delegations": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every babylon_list_delegations call is checked against it from then on.

FAQ

Questions about babylon_list_delegations

What does the babylon_list_delegations tool do? +

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.

How do I enforce a policy on babylon_list_delegations? +

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.

What risk level is babylon_list_delegations? +

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

Can I rate-limit babylon_list_delegations? +

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.

How do I block babylon_list_delegations completely? +

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.

What MCP server provides babylon_list_delegations? +

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.

KEEP EXPLORING

More on Tenzro Ledger, and thousands of servers like it.

This server

All 360 Tenzro Ledger tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →