hires_publish_to_job_board
Activate selected job boards for a job. Sets boards to activation queue state. Use for controlled multi-board publishing workflows.
This record as markdown: /tools/com-100hires-100hires/hires-publish-to-job-board.md
What hires_publish_to_job_board does on 100Hires - AI ATS & Recruitment Software
AI agents use hires_publish_to_job_board 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 |
boards | array | — | Array of board identifiers to activate (e.g. ['indeed', 'linkedin']) |
Parameters from the server's own tool schema.
Why hires_publish_to_job_board is rated Medium
This tool creates or modifies job board publishing state—a reversible operation that does not delete data or execute arbitrary code. While publishing to job boards has business impact (increases job visibility, may generate recruitment costs), it is a standard Write operation common to ATS platforms.
From the tool's definition 'Activate selected job boards for a job' and 'Sets boards to activation queue state' indicate the tool modifies the state of job boards by activating them for publication, which is a reversible configuration change.
Attacks that exploit this kind of access
The rule that runs hires_publish_to_job_board 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_publish_to_job_board, this is the rule to start with:
hires_publish_to_job_board 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_publish_to_job_board call is checked against it from then on.
Questions about hires_publish_to_job_board
Activate selected job boards for a job. Sets boards to activation queue state. Use for controlled multi-board publishing 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.
hires_publish_to_job_board accepts 2 parameters: id, boards. 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_publish_to_job_board: 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_publish_to_job_board 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_publish_to_job_board 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_publish_to_job_board. 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_publish_to_job_board 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