get_node_status

Get the current node status including block height, peer count, uptime, and role.

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/get-node-status.md

WHAT IT DOES

What get_node_status does on Tenzro Ledger MCP

AI agents call get_node_status 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 get_node_status is rated Low

This tool performs a read-only query of node status metrics. It retrieves data (block height, peer count, uptime, role) without creating, modifying, deleting, executing code, or affecting financial state. The verb 'Get' and absence of any mutating or executing language confirms this is a Read operation with minimal blast radius if misused.

From the tool's definition Tool name 'get_node_status' and description 'Get the current node status including block height, peer count, uptime, and role' indicate a query operation that retrieves node state information with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_node_status 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 get_node_status, this is the rule to start with:

get_node_status Allowed

get_node_status 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": {
    "get_node_status": {}
  }
}

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 get_node_status call is checked against it from then on.

FAQ

Questions about get_node_status

What does the get_node_status tool do? +

Get the current node status including block height, peer count, uptime, and role. 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 get_node_status? +

Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for get_node_status: 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 get_node_status? +

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

Can I rate-limit get_node_status? +

Yes. Add a rate_limit block to the get_node_status 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 get_node_status completely? +

Set action: deny in the PolicyLayer policy for get_node_status. 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 get_node_status? +

get_node_status 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

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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