node_profile
Return the local node's hardware self-profile and derived serving values.
This record as markdown: /tools/network-tenzro-tenzro/node-profile.md
What node_profile does on Tenzro Ledger MCP
AI agents call node_profile 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.
Why node_profile is rated Low
This tool queries and returns information about the local node's hardware configuration and performance metrics. It is purely informational with no side effects, no data modification, no code execution, and no financial implications. The blast radius of misuse is minimal — an attacker would only gain visibility into hardware characteristics, which does not enable further system compromise or data loss.
From the tool's definition Tool description states 'Return the local node's hardware self-profile and derived serving values' — a retrieval operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs node_profile 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 node_profile, this is the rule to start with:
node_profile is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every node_profile call is checked against it from then on.
Questions about node_profile
Return the local node's hardware self-profile and derived serving values. 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 node_profile: 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.
node_profile 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 node_profile 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 node_profile. 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.
node_profile 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.
More on Tenzro Ledger, and thousands of servers like it.
This server
Across the catalogue