homebox_create_item
AI agents use homebox_create_item 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.
The tool creates new items in the Homebox inventory system, which is a reversible Write operation. While the description is empty (reducing confidence slightly), the naming convention and context from sibling tools clearly establish this as item creation functionality.
From the tool's definition Tool name 'homebox_create_item' indicates creation of new inventory items. Sibling tools include destructive operations (homebox_delete_item, homebox_delete_label, homebox_delete_location) and read operations (homebox_get_item, homebox_list_items),…
Attacks that exploit this kind of access
homebox_create_item. 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_item: 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_item 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_item 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_item. 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_item 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 →