AI agents call get_inventory_summary to retrieve information from Homelab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation on the homelab inventory. It retrieves and aggregates metadata (counts and structure) without any side effects, data modification, or execution of commands. The read-only nature and informational purpose classify it as a Read category tool with low severity, as misuse would at worst expose infrastructure topology details but cannot alter systems or trigger actions.
From the tool's definition Tool description states 'Get a high-level summary of the inventory including counts and structure' - purely retrieval of summary data with no modification, execution, or deletion capabilities.
Attacks that exploit this kind of access
Get a high-level summary of the inventory including counts and structure. It is categorised as a Read tool in the Homelab MCP Server, which means it retrieves data without modifying state.
Register the Homelab MCP server in PolicyLayer and add a rule for get_inventory_summary: 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. Nothing to install.
get_inventory_summary 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 get_inventory_summary 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 get_inventory_summary. 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.
get_inventory_summary is provided by the Homelab MCP server (myraffy/homelab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →