AI agents call list_job_roles 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 job role data from the HRIS system without side effects. It is a simple query/list operation consistent with the read-only nature of the server. The optional personId filter does not change the fundamental read-only behavior. Severity is low because job role information is typically non-sensitive HR metadata with limited blast radius if misused.
From the tool's definition Tool description states 'List job roles' with optional filtering; server description emphasizes 'Read-only MCP server' for querying data; no modification, deletion, or execution capability described.
Attacks that exploit this kind of access
List job roles (historical and current job assignments). Optionally filter by personId. 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_job_roles: 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_job_roles 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_job_roles 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_job_roles. 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_job_roles 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 →