AI agents use relocate_employee_desk to create or update resources in Hilanet MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hilanet MCP environment.
This tool modifies employee state (desk/workspace assignment) reversibly—relocations can be undone by moving the employee back. While it could cause workplace disruption or stress, it does not delete data, execute code, incur financial costs, or cause irreversible harm. The satirical corporate context reinforces that this simulates reversible administrative action rather than destructive consequences.
From the tool's definition Tool name 'relocate_employee_desk' and description 'Move someone' indicate a modification action that reassigns an employee's physical workspace location.
Documented attack patterns abuse exactly the kind of access relocate_employee_desk gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Hilanet MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for relocate_employee_desk:
{
"version": "1",
"default": "deny",
"tools": {
"relocate_employee_desk": {
"limits": [
{
"counter": "relocate_employee_desk_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}relocate_employee_desk stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Move someone. It is categorised as a Write tool in the Hilanet MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hilanet MCP server in PolicyLayer and add a rule for relocate_employee_desk: 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 Hilanet MCP. Nothing to install.
relocate_employee_desk 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 relocate_employee_desk 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 relocate_employee_desk. 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.
relocate_employee_desk is provided by the Hilanet MCP server (adird/hilanet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Hilanet MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 Hilanet MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.