hires_set_job_status

Change job status via dedicated endpoint. Recommended for publish/unpublish/archive transitions and status automation workflows.

SERVER100Hires - AI ATS & Recruitment Software SOURCEhttps://mcp.100hires.com/mcp

Medium RISK CLASS

Category Write

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-100hires-100hires/hires-set-job-status.md

WHAT IT DOES

What hires_set_job_status does on 100Hires - AI ATS & Recruitment Software

AI agents use hires_set_job_status 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
`status`	string	Yes	New job status (e.g. Draft, Public, Archived). See GET /taxonomy/statuses.
`include`	string	—	Comma-separated related resources to embed: workflow, hiring_team, pipeline_stages

Parameters from the server's own tool schema.

RISK

Why hires_set_job_status is rated Medium

The tool modifies the status property of job records, which affects visibility and operational state. While reversible (jobs can be unpublished or transitioned between states), it impacts recruitment workflows significantly—unpublishing a job stops applications, archiving removes it from active consideration. The ability to change job visibility and status affects organizational processes.

From the tool's definition Tool description states "Change job status" and is "Recommended for publish/unpublish/archive transitions". The verb "Change" and the specific mention of status transitions (publish, unpublish, archive) indicate modification of job state data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hires_set_job_status 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_set_job_status, this is the rule to start with:

hires_set_job_status Rate-limited

hires_set_job_status 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hires_set_job_status": {
      "limits": [
        {
          "counter": "hires_set_job_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 100Hires - AI ATS & Recruitment Software, apply this rule, and every hires_set_job_status call is checked against it from then on.

FAQ

Questions about hires_set_job_status

What does the hires_set_job_status tool do? +

Change job status via dedicated endpoint. Recommended for publish/unpublish/archive transitions and status automation workflows. 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.

What parameters does hires_set_job_status accept? +

hires_set_job_status accepts 3 parameters: id, status, include. Required: id, status. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hires_set_job_status? +

Register the 100Hires - AI ATS & Recruitment Software MCP server in PolicyLayer and add a rule for hires_set_job_status: 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.

What risk level is hires_set_job_status? +

hires_set_job_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hires_set_job_status? +

Yes. Add a rate_limit block to the hires_set_job_status 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.

How do I block hires_set_job_status completely? +

Set action: deny in the PolicyLayer policy for hires_set_job_status. 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.

What MCP server provides hires_set_job_status? +

hires_set_job_status 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.

KEEP EXPLORING

More on 100Hires - AI ATS & Recruitment Software, and thousands of servers like it.

This server

All 133 100Hires - AI ATS & Recruitment Software tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →