hires_list_hiring_team
List users currently assigned to a job's hiring team. Useful for notification routing and collaboration tooling.
This record as markdown: /tools/com-100hires-100hires/hires-list-hiring-team.md
What hires_list_hiring_team does on 100Hires - AI ATS & Recruitment Software
AI agents call hires_list_hiring_team to retrieve information from 100Hires - AI ATS & Recruitment Software without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | number | Yes | Job ID (numeric) or alias |
Parameters from the server's own tool schema.
Why hires_list_hiring_team is rated Low
This tool retrieves organizational team membership information for a specific job. It has no side effects, does not modify data, and does not trigger external operations. The most severe risk is potential information disclosure of internal team members, but the data returned is typically internal HR/recruiting staff already involved with the job posting, making the blast radius low for an AI agent misuse scenario.
From the tool's definition Tool description states 'List users currently assigned to a job's hiring team' — it retrieves/queries user data without modifying or deleting anything. The verb 'list' is explicitly read-only.
Attacks that exploit this kind of access
The rule that runs hires_list_hiring_team safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 100Hires - AI ATS & Recruitment Software, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hires_list_hiring_team, this is the rule to start with:
hires_list_hiring_team 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 100Hires - AI ATS & Recruitment Software, apply this rule, and every hires_list_hiring_team call is checked against it from then on.
Questions about hires_list_hiring_team
List users currently assigned to a job's hiring team. Useful for notification routing and collaboration tooling. It is categorised as a Read tool in the 100Hires - AI ATS & Recruitment Software MCP Server, which means it retrieves data without modifying state.
hires_list_hiring_team accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the 100Hires - AI ATS & Recruitment Software MCP server in PolicyLayer and add a rule for hires_list_hiring_team: 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 100Hires - AI ATS & Recruitment Software. Nothing to install.
hires_list_hiring_team 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 hires_list_hiring_team 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 hires_list_hiring_team. 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.
hires_list_hiring_team is provided by the 100Hires - AI ATS & Recruitment Software MCP server (https://mcp.100hires.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 100Hires - AI ATS & Recruitment Software, and thousands of servers like it.
Across the catalogue