list_humaans_people
List employees from Humaans HR. By default returns only active employees. Use status filter for other groups. Returns compact summaries: id, name, email, job title, department, teams, location, status. Example: {
This record as markdown: /tools/freshdesk/list-humaans-people.md
What list_humaans_people does on Freshdesk
AI agents call list_humaans_people to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_humaans_people is rated Low
This tool retrieves and queries employee data from an HR system without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval operation with filtering options. The blast radius of misuse is low—exposure of employee directories is a concern but limited compared to tools that could modify or delete records.
From the tool's definition Tool description states it 'List employees from Humaans HR' and 'Returns compact summaries' of employee data. The verb 'list' and the read-only nature of querying employee records with no modification capability are clear indicators.
Attacks that exploit this kind of access
The rule that runs list_humaans_people safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_humaans_people, this is the rule to start with:
list_humaans_people is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every list_humaans_people call is checked against it from then on.
Questions about list_humaans_people
List employees from Humaans HR. By default returns only active employees. Use status filter for other groups. Returns compact summaries: id, name, email, job title, department, teams, location, status. Example: {. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for list_humaans_people: 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 Freshdesk. Nothing to install.
list_humaans_people 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_humaans_people 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_humaans_people. 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_humaans_people is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue