Set or change the parent item for an item. This creates a parent-child relationship where the item becomes a child of another item (e.g., putting an item inside a box).
AI agents use set_item_parent 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.
An AI agent can call set_item_parent faster than any human can review — one bad instruction and it creates or modifies resources in Homebox MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Set or change the parent item for an item. This creates a parent-child relationship where the item becomes a child of another item (e.g., putting an item inside a box). 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 set_item_parent: 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.
set_item_parent 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 set_item_parent 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 set_item_parent. 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.
set_item_parent is provided by the Homebox MCP Server MCP server (supermaxman/homebox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.