Get the power and HDD LED status of the target machine.
AI agents call nanokvm_led_status to retrieve information from NanoKVM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries the current LED status indicators (power and HDD) of the remote machine. It has no side effects, does not modify any configuration or data, does not execute code or commands, and does not delete or move resources. It is a simple informational retrieval operation, making it a Read category tool with low severity since misuse would only expose status information that is typically non-sensitive.
From the tool's definition The tool name 'nanokvm_led_status' and description 'Get the power and HDD LED status of the target machine' indicate a read-only operation that retrieves status information without modifying any state or triggering actions.
Documented attack patterns abuse exactly the kind of access nanokvm_led_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and NanoKVM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for nanokvm_led_status:
{
"version": "1",
"default": "deny",
"tools": {
"nanokvm_led_status": {}
}
}nanokvm_led_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the power and HDD LED status of the target machine. It is categorised as a Read tool in the NanoKVM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NanoKVM MCP Server MCP server in PolicyLayer and add a rule for nanokvm_led_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 NanoKVM MCP Server. Nothing to install.
nanokvm_led_status 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 nanokvm_led_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.
Set action: deny in the PolicyLayer policy for nanokvm_led_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.
nanokvm_led_status is provided by the NanoKVM MCP Server MCP server (scgreenhalgh/nanokvm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from NanoKVM MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
19 NanoKVM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.