Increase your salary by a specified percentage or amount
AI agents use increase_salary 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 creates or modifies financial records (salary data) in a reversible manner. While it involves salary (a financial metric), the action itself is a data modification rather than an irreversible deletion or an actual money transfer. The satirical context does not change the underlying action: it modifies employee compensation records.
From the tool's definition Tool name 'increase_salary' and description 'Increase your salary by a specified percentage or amount' directly indicate modification of compensation data.
Documented attack patterns abuse exactly the kind of access increase_salary 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 increase_salary:
{
"version": "1",
"default": "deny",
"tools": {
"increase_salary": {
"limits": [
{
"counter": "increase_salary_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} increase_salary 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.
Increase your salary by a specified percentage or amount. 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 increase_salary: 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.
increase_salary 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 increase_salary 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 increase_salary. 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.
increase_salary 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.