hires_create_interview
Schedule an interview for an application. The location is matched to an existing record or created.
This record as markdown: /tools/com-100hires-100hires/hires-create-interview.md
What hires_create_interview does on 100Hires - AI ATS & Recruitment Software
AI agents use hires_create_interview 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 | number | Yes | |
include | string | — | Embed: candidate, application, job |
end_time | number | Yes | Unix seconds, after start_time |
location | string | — | Free text |
start_time | number | Yes | Unix seconds |
interviewer_ids | array | Yes | Interviewer user ids |
Parameters from the server's own tool schema.
Why hires_create_interview is rated Medium
An AI agent can call hires_create_interview faster than any human can review: one bad instruction and it creates or modifies resources in 100Hires - AI ATS & Recruitment Software by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs hires_create_interview 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_create_interview, this is the rule to start with:
hires_create_interview 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_create_interview call is checked against it from then on.
Questions about hires_create_interview
Schedule an interview for an application. The location is matched to an existing record or created. 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_create_interview accepts 6 parameters: id, include, end_time, location, start_time, interviewer_ids. Required: id, end_time, start_time, interviewer_ids. 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_create_interview: 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_create_interview 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_create_interview 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_create_interview. 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_create_interview 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