Subject self-read of the caller's own Chainlink/bridge analytics.
AI agents call get_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.
This tool allows the caller to query their own bridge analytics data. The 'self-read' language and lack of any write, execute, or financial operation language clearly indicate this is a Read operation. The scope is limited to the caller's own data, which reduces severity. There are no destructive, executable, or financial implications.
From the tool's definition Tool description explicitly states "self-read of the caller's own" analytics data, indicating retrieval of existing data with no modification or side effects.
Attacks that exploit this kind of access
Subject self-read of the caller's own Chainlink/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 get_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.
get_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 get_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 get_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.
get_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 →