AI agents call list_compensation_types 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 only retrieves and lists compensation type configurations. It has no side effects, cannot modify data, and poses minimal risk even if an AI agent misuses it by querying it excessively or repeatedly. The worst outcome would be information disclosure of what compensation types exist in the system, which is typically non-sensitive metadata in an HRIS context.
From the tool's definition Tool description states 'List all compensation types configured in the account' - a retrieval operation. Server is explicitly described as 'Read-only MCP server'. The tool queries configuration data without modifying or executing anything.
Attacks that exploit this kind of access
List all compensation types configured in the account (salary, bonus, commission, equity, etc.). 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 list_compensation_types: 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.
list_compensation_types 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 list_compensation_types 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 list_compensation_types. 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.
list_compensation_types 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →