list_bridge_analytics
AI agents call list_bridge_analytics 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 name structure ('list_*') strongly suggests a data retrieval function that queries bridge analytics information without side effects. However, confidence is slightly reduced (0.75) because the description is empty and we cannot verify what 'bridge_analytics' specifically returns or whether it has any operational constraints.
From the tool's definition Tool name 'list_bridge_analytics' contains the verb 'list', which is a read operation that queries and retrieves data. No modification or execution capability is indicated.
Attacks that exploit this kind of access
list_bridge_analytics. 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_analytics: 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_analytics 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_analytics 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_analytics. 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_analytics 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 →