get_humaans_job_role
Get a specific job role by ID from Humaans. Returns: job title, department, manager (reportingTo), effectiveDate, endDate, note. Example: {
This record as markdown: /tools/freshdesk/get-humaans-job-role.md
What get_humaans_job_role does on Freshdesk
AI agents call get_humaans_job_role 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_job_role is rated Low
This tool retrieves and queries job role information from Humaans by ID. It has no side effects, creates no data modifications, executes no external operations, and triggers no financial transactions. It is a pure read operation with minimal risk if misused by an AI agent—exposure of HR metadata could have privacy concerns but the tool itself performs only data retrieval.
From the tool's definition Tool name 'get_humaans_job_role' and description 'Get a specific job role by ID from Humaans' indicate a retrieval operation. Returns job metadata (title, department, manager, dates, note) with no modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs get_humaans_job_role 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_job_role, this is the rule to start with:
get_humaans_job_role 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_job_role call is checked against it from then on.
Questions about get_humaans_job_role
Get a specific job role by ID from Humaans. Returns: job title, department, manager (reportingTo), effectiveDate, endDate, note. 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_job_role: 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_job_role 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_job_role 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_job_role. 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_job_role 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