list_bridge_sponsorship_pools
AI agents call list_bridge_sponsorship_pools 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 'list_' prefix indicates a read-only query operation that retrieves or enumerates sponsorship pools for bridge operations. Even within a financial context (Tenzro Ledger), listing pools is a non-destructive information retrieval with minimal blast radius.
From the tool's definition Tool name 'list_bridge_sponsorship_pools' uses the verb 'list', which is a retrieval operation. The empty description prevents confirmation of side effects, but the naming strongly suggests querying bridge sponsorship pool data without modification.
Attacks that exploit this kind of access
list_bridge_sponsorship_pools. 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 list_bridge_sponsorship_pools: 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.
list_bridge_sponsorship_pools 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 list_bridge_sponsorship_pools 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 list_bridge_sponsorship_pools. 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.
list_bridge_sponsorship_pools 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 →