Request to work extra hours for free to demonstrate your commitment
AI agents use request_unpaid_overtime 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 simulates creating a request or record of unpaid overtime work within a satirical HR system. It is Write-category because it modifies data (work schedules, HR records) in a reversible manner—requests can be withdrawn or modified.
From the tool's definition Tool name is 'request_unpaid_overtime' and description states it 'Request[s] to work extra hours for free'. This creates or modifies data (work schedule/records) reversibly within the simulated corporate system.
Documented attack patterns abuse exactly the kind of access request_unpaid_overtime 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 request_unpaid_overtime:
{
"version": "1",
"default": "deny",
"tools": {
"request_unpaid_overtime": {
"limits": [
{
"counter": "request_unpaid_overtime_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}request_unpaid_overtime 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.
Request to work extra hours for free to demonstrate your commitment. 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 request_unpaid_overtime: 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.
request_unpaid_overtime 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 request_unpaid_overtime 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 request_unpaid_overtime. 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.
request_unpaid_overtime 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.