Submit a formal complaint about your manager that may lead to termination
AI agents use fire_my_manager 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.
The tool writes/creates a formal complaint document in a system, which is a reversible write operation (complaints can be retracted, amended, or dismissed). Although the *outcome* of such a complaint might be termination (destructive), the tool itself performs a Write action: submission of a formal complaint.
From the tool's definition Tool description states 'Submit a formal complaint about your manager that may lead to termination' — this creates a formal record/complaint that modifies HR/personnel data and triggers downstream consequences.
Documented attack patterns abuse exactly the kind of access fire_my_manager 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 fire_my_manager:
{
"version": "1",
"default": "deny",
"tools": {
"fire_my_manager": {
"limits": [
{
"counter": "fire_my_manager_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}fire_my_manager 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.
Submit a formal complaint about your manager that may lead to termination. 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 fire_my_manager: 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.
fire_my_manager 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 fire_my_manager 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 fire_my_manager. 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.
fire_my_manager 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.