hires_add_hiring_team_member
Add a company member to the job's hiring team. Use in workflow setup and ownership automation.
This record as markdown: /tools/com-100hires-100hires/hires-add-hiring-team-member.md
What hires_add_hiring_team_member does on 100Hires - AI ATS & Recruitment Software
AI agents use hires_add_hiring_team_member to create or update resources in 100Hires - AI ATS & Recruitment Software, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 100Hires - AI ATS & Recruitment Software environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | number | Yes | Job ID (numeric) or alias |
user_id | number | Yes | User ID to add to the hiring team. |
Parameters from the server's own tool schema.
Why hires_add_hiring_team_member is rated Medium
This tool modifies recruitment team assignments for a job—a reversible write operation. It does not execute external code, delete data, move money, or retrieve information. The blast radius is medium because misconfiguration could grant unintended users access to hiring decisions, but the action is reversible by removing the team member.
From the tool's definition Tool name 'hires_add_hiring_team_member' and description 'Add a company member to the job's hiring team' indicate creation/modification of team membership records.
Attacks that exploit this kind of access
The rule that runs hires_add_hiring_team_member 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_add_hiring_team_member, this is the rule to start with:
hires_add_hiring_team_member stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_add_hiring_team_member call is checked against it from then on.
Questions about hires_add_hiring_team_member
Add a company member to the job's hiring team. Use in workflow setup and ownership automation. It is categorised as a Write tool in the 100Hires - AI ATS & Recruitment Software MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
hires_add_hiring_team_member accepts 2 parameters: id, user_id. Required: id, user_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_add_hiring_team_member: 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_add_hiring_team_member is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the hires_add_hiring_team_member 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_add_hiring_team_member. 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_add_hiring_team_member 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