homebox_get_location_tree
AI agents call homebox_get_location_tree to retrieve information from Homebox MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves location hierarchy information from the Homebox inventory system. It performs a read-only query with no side effects—it cannot modify, delete, or execute operations. The blast radius of misuse is minimal: an AI agent could only access location structure data it is already authorized to see.
From the tool's definition Tool name 'homebox_get_location_tree' contains 'get', indicating a retrieval operation. Description is empty, but the sibling tool 'homebox_get_location' and the naming pattern suggest this retrieves hierarchical location data without modification.
Attacks that exploit this kind of access
homebox_get_location_tree. It is categorised as a Read tool in the Homebox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Homebox MCP Server MCP server in PolicyLayer and add a rule for homebox_get_location_tree: 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 Homebox MCP Server. Nothing to install.
homebox_get_location_tree 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 homebox_get_location_tree 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 homebox_get_location_tree. 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.
homebox_get_location_tree is provided by the Homebox MCP Server MCP server (oangelo/homebox-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 →