AI agents call list_time_away 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 queries and retrieves time-away records without side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The low severity reflects minimal blast radius—an AI agent misuse would only expose HR time-away data already within the system's scope, not cause operational harm or financial loss.
From the tool's definition Tool name 'list_time_away' and description 'List time-away records' with optional query filters (personId, startDate, endDate) indicate retrieval only. Server is explicitly described as 'Read-only MCP server'.
Attacks that exploit this kind of access
List time-away records. Optional filters: personId, startDate, endDate (YYYY-MM-DD). 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_time_away: 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_time_away 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_time_away 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_time_away. 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_time_away 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 →