disk_smart_test_run
Run a SMART test on one or more disks. Returns a job ID for the test.
This record as markdown: /tools/nasbridge/disk-smart-test-run.md
What disk_smart_test_run does on Nasbridge
AI agents invoke disk_smart_test_run to trigger actions in Nasbridge. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why disk_smart_test_run is rated High
This tool triggers an external hardware diagnostic operation (SMART test) on physical disks. It executes a job/process rather than simply reading data or modifying configuration. While SMART tests are generally non-destructive, running them can impact disk performance and involves executing a background job on hardware devices.
From the tool's definition Run a SMART test on one or more disks. Returns a job ID for the test.
Attacks that exploit this kind of access
The rule that runs disk_smart_test_run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For disk_smart_test_run, this is the rule to start with:
disk_smart_test_run stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every disk_smart_test_run call is checked against it from then on.
Questions about disk_smart_test_run
Run a SMART test on one or more disks. Returns a job ID for the test. It is categorised as a Execute tool in the Nasbridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nasbridge MCP server in PolicyLayer and add a rule for disk_smart_test_run: 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 Nasbridge. Nothing to install.
disk_smart_test_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the disk_smart_test_run 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 disk_smart_test_run. 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.
disk_smart_test_run is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
Across the catalogue