homebox_create_location
AI agents use homebox_create_location to create or update resources in Homebox MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Homebox MCP Server environment.
Creating locations in an inventory system is a reversible Write operation. It modifies the system state by adding new data but does not delete, execute arbitrary code, or trigger financial transactions. Severity is medium because misuse could create many spurious location records cluttering the inventory, though the operation remains reversible via the homebox_delete_location sibling tool.
From the tool's definition Tool name 'homebox_create_location' indicates creation of data; paired with sibling delete/get/list operations on the Homebox inventory system, this tool creates location records within an inventory management system.
Attacks that exploit this kind of access
homebox_create_location. It is categorised as a Write tool in the Homebox MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Homebox MCP Server MCP server in PolicyLayer and add a rule for homebox_create_location: 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_create_location is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the homebox_create_location 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_create_location. 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_create_location 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 →