AI agents call scan_disk to retrieve information from HomeLab Monitor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description creating some uncertainty, the tool name suggests disk scanning/inspection rather than modification. The server is explicitly described as read-only for monitoring purposes, and all sibling tools are data retrieval operations. A disk scan in a monitoring context typically queries disk usage and health metrics without modification.
From the tool's definition Tool name 'scan_disk' suggests retrieval of disk information; context indicates a 'read-only MCP server' for monitoring; sibling tools are all get_* queries with no side effects.
Documented attack patterns abuse exactly the kind of access scan_disk gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HomeLab Monitor, and nothing reaches the server without passing your rules. This is the rule we recommend for scan_disk:
{
"version": "1",
"default": "deny",
"tools": {
"scan_disk": {}
}
}scan_disk 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.
scan_disk. It is categorised as a Read tool in the HomeLab Monitor MCP Server, which means it retrieves data without modifying state.
Register the HomeLab Monitor MCP server in PolicyLayer and add a rule for scan_disk: 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 HomeLab Monitor. Nothing to install.
scan_disk 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 scan_disk 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 scan_disk. 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.
scan_disk is provided by the HomeLab Monitor MCP server (sikamikanikobg/homelab-monitor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 HomeLab Monitor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 HomeLab Monitor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.