Combined health probe — /livez, /readyz, /v2/version. Returns
AI agents call canton_health 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 is a diagnostic/monitoring tool that queries the health and version status of a service. It retrieves information only and causes no state changes, data modifications, or external operations. The endpoints are read-only probes typical of health check infrastructure. Despite the server's overall sensitive nature (payments, staking, bridges), this specific tool is purely observational.
From the tool's definition Tool description indicates it performs health checks via `/livez`, `/readyz`, and `/v2/version` endpoints — these are standard diagnostic endpoints that retrieve status information without side effects.
Attacks that exploit this kind of access
Combined health probe — /livez, /readyz, /v2/version. Returns. 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 canton_health: 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.
canton_health 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 canton_health 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 canton_health. 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.
canton_health 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 →