AI agents call list_emergency_contacts 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 emergency contact information without modifying, deleting, or executing any operations. It is a standard read operation consistent with the server's read-only nature. Severity is low because emergency contacts are typically not sensitive enough to warrant higher classification in isolation, though context-dependent risk exists.
From the tool's definition Server is described as 'Read-only MCP server' and tool 'list_emergency_contacts' retrieves/queries emergency contact data with optional filtering. No mutations, deletions, or side effects.
Attacks that exploit this kind of access
List emergency contacts. 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_emergency_contacts: 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_emergency_contacts 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_emergency_contacts 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_emergency_contacts. 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_emergency_contacts 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 →