check_ssd_health
utilpeek: Check an SSD's wear from smartctl or nvme smart-log. Returns SSD wear from smartctl or nvme smart-log text/JSON: percentage used (can pass the full rated endurance), host TB written (NVMe data units × 512,000 bytes / 10^12), optional rated-TBW share and gap, spare vs threshold, warnings...
This record as markdown: /tools/dev-tanod-tanod/check-ssd-health.md
What check_ssd_health does on Tanod
AI agents call check_ssd_health to retrieve information from Tanod without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
report | string | Yes | smartctl -a/-j or nvme smart-log text or JSON. No commands run or URLs fetched. |
rated_tbw | object | — | Optional maker's rated endurance in decimal TB written (TBW). |
Parameters from the server's own tool schema.
Why check_ssd_health is rated Low
Even though check_ssd_health only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs check_ssd_health safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_ssd_health, this is the rule to start with:
check_ssd_health 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 Tanod, apply this rule, and every check_ssd_health call is checked against it from then on.
Questions about check_ssd_health
utilpeek: Check an SSD's wear from smartctl or nvme smart-log. Returns SSD wear from smartctl or nvme smart-log text/JSON: percentage used (can pass the full rated endurance), host TB written (NVMe data units × 512,000 bytes / 10^12), optional rated-TBW share and gap, spare vs threshold, warnings, errors, shutdowns and hours, with an ok / worn / failing verdict and reasons. Only the pasted report is read; no commands run or network calls. SMART PASSED does not rule out failure; SATA wear is vendor-specific. Invalid reports/ratings: 422, not charged. Shares the utilpeek free pool. Typically under 0.1 s. Price: USD 0.002. Free: 10 utilpeek calls per IP per UTC day. The submitted text is never logged or stored. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
check_ssd_health accepts 2 parameters: report, rated_tbw. Required: report. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for check_ssd_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 Tanod. Nothing to install.
check_ssd_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 check_ssd_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 check_ssd_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.
check_ssd_health is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue