wormhole_ntt_list_chains
AI agents call wormhole_ntt_list_chains 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 tool appears to list available chains in a Wormhole NTT (Native Token Transfer) context. Listing/enumerating data without modifying it is a read operation. The empty description reduces confidence, but the naming convention strongly suggests data retrieval with no side effects. Low severity because listing chains poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'wormhole_ntt_list_chains' contains 'list' which is a read operation pattern. Description is empty, limiting confidence.
Attacks that exploit this kind of access
wormhole_ntt_list_chains. 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 wormhole_ntt_list_chains: 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.
wormhole_ntt_list_chains 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 wormhole_ntt_list_chains 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 wormhole_ntt_list_chains. 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.
wormhole_ntt_list_chains 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 →