AI agents call find_person_by_email 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 performs a simple data retrieval operation—looking up a person by email in an HRIS system and returning their object. It is purely informational with no capability to modify, delete, or execute operations. It matches the 'Read' category definition: 'retrieves or queries data; no side effects.'
From the tool's definition Tool description states 'Find one person by exact email match. Returns the person object, or null if not found.' The action is a query that retrieves data without modification. Server description confirms it is a 'Read-only MCP server'.
Attacks that exploit this kind of access
Find one person by exact email match. Returns the person object, or null if not found. 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 find_person_by_email: 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.
find_person_by_email 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 find_person_by_email 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 find_person_by_email. 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.
find_person_by_email 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 →