hires_create_job
Create a job with taxonomy, location, salary, and workflow configuration. Primary endpoint for programmatic job publishing. Required fields: status, title, description, location_city, location_country.
This record as markdown: /tools/100hires-mcp-server/hires-create-job.md
What hires_create_job does on 100Hires MCP Server
AI agents use hires_create_job to create or update resources in 100Hires MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 100Hires MCP Server environment.
Why hires_create_job is rated Medium
This tool creates new job records in the 100Hires ATS with required fields (status, title, description, location, country). Job creation is a reversible write operation—jobs can typically be deleted, archived, or unpublished. While job creation could have downstream effects (publishing to boards, attracting candidates), the tool itself performs data creation rather than deletion or external financial transactions.
From the tool's definition Tool name is 'hires_create_job' and description states it will 'Create a job' with configuration parameters.
Attacks that exploit this kind of access
The rule that runs hires_create_job safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 100Hires MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hires_create_job, this is the rule to start with:
hires_create_job 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 MCP Server, apply this rule, and every hires_create_job call is checked against it from then on.
Questions about hires_create_job
Create a job with taxonomy, location, salary, and workflow configuration. Primary endpoint for programmatic job publishing. Required fields: status, title, description, location_city, location_country. It is categorised as a Write tool in the 100Hires MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 100Hires MCP Server MCP server in PolicyLayer and add a rule for hires_create_job: 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 MCP Server. Nothing to install.
hires_create_job 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_job 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_job. 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_job is provided by the 100Hires MCP Server MCP server (100hires/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 100Hires MCP Server, and thousands of servers like it.
This server
Across the catalogue