get_humaans_person
Get full employee profile from Humaans by their ID. Returns detailed profile including: name, email, job role, department, teams, location, employment dates, contract type, working days, manager, bio, social links. Sensitive fields (tax ID, personal email, home address) are redacted for privacy. ...
This record as markdown: /tools/freshdesk/get-humaans-person.md
What get_humaans_person does on Freshdesk
AI agents call get_humaans_person 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 get_humaans_person is rated Low
This is a Read category tool because it retrieves employee profile data without creating, modifying, deleting, or executing any operations. However, severity is medium rather than low due to the sensitive nature of the returned personal and organizational data (email, job role, department, manager relationships, employment dates, location, bio).
From the tool's definition Tool description explicitly states it 'Get[s] full employee profile from Humaans by their ID' and 'Returns detailed profile including: name, email, job role, department, teams, location, employment dates, contract type, working days, manager, bio, social…
Attacks that exploit this kind of access
The rule that runs get_humaans_person 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 get_humaans_person, this is the rule to start with:
get_humaans_person 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 get_humaans_person call is checked against it from then on.
Questions about get_humaans_person
Get full employee profile from Humaans by their ID. Returns detailed profile including: name, email, job role, department, teams, location, employment dates, contract type, working days, manager, bio, social links. Sensitive fields (tax ID, personal email, home address) are redacted for privacy. 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 get_humaans_person: 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.
get_humaans_person 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 get_humaans_person 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 get_humaans_person. 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.
get_humaans_person 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