canton_health

Combined health probe — /livez, /readyz, /v2/version. Returns

SERVERTenzro Ledger MCP SOURCEhttps://canton-mcp.tenzro.network/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/network-tenzro-tenzro/canton-health.md

WHAT IT DOES

What canton_health does on Tenzro Ledger MCP

AI agents call canton_health to retrieve information from Tenzro Ledger MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why canton_health is rated Low

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

RECOMMENDED RULE

The rule that runs canton_health safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For canton_health, this is the rule to start with:

canton_health Allowed

canton_health is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "canton_health": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every canton_health call is checked against it from then on.

FAQ

Questions about canton_health

What does the canton_health tool do? +

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.

How do I enforce a policy on canton_health? +

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.

What risk level is canton_health? +

canton_health is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit canton_health? +

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.

How do I block canton_health completely? +

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.

What MCP server provides canton_health? +

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.

KEEP EXPLORING

More on Tenzro Ledger, and thousands of servers like it.

This server

All 360 Tenzro Ledger tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →