AI agents use block_promotion 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.
Although satirical, this tool modifies organizational data (blocking someone's promotion status/prospects), which is a reversible write operation affecting personnel records. It is not destructive (the record itself isn't deleted), not financial (no direct money movement), and not execute (not running arbitrary code).
From the tool's definition Tool name and description: 'block_promotion' - 'Subtly prevent a colleague from getting promoted'. This modifies employment/HR status of another person by preventing promotion eligibility or advancement.
Documented attack patterns abuse exactly the kind of access block_promotion 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 block_promotion:
{
"version": "1",
"default": "deny",
"tools": {
"block_promotion": {
"limits": [
{
"counter": "block_promotion_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}block_promotion 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.
Subtly prevent a colleague from getting promoted. 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 block_promotion: 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.
block_promotion 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 block_promotion 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 block_promotion. 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.
block_promotion 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.