AI agents call get_compensation to retrieve information from Humaans without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves compensation data without modifying, deleting, or executing operations. It is a simple read/query operation on an HRIS system. The low severity reflects minimal blast radius—compensation data disclosure is sensitive but exposure of a single record via query does not cause irreversible harm or financial movement.
From the tool's definition Tool name 'get_compensation' and description 'Retrieve a single compensation record by id' indicate a read-only query operation. Server description explicitly states 'Read-only MCP server' with tools to 'query' compensation and other data.
Attacks that exploit this kind of access
Retrieve a single compensation record by id. It is categorised as a Read tool in the Humaans MCP Server, which means it retrieves data without modifying state.
Register the Humaans MCP server in PolicyLayer and add a rule for get_compensation: 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 Humaans. Nothing to install.
get_compensation is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_compensation 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 get_compensation. 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.
get_compensation is provided by the Humaans MCP server (ptorsten/humaans-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_compensation is one line of Humaans's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →