hires_list_workflow_stages
List pipeline stages filtered by workflow or job. Useful for transition UIs and workflow validation.
This record as markdown: /tools/com-100hires-100hires/hires-list-workflow-stages.md
What hires_list_workflow_stages does on 100Hires - AI ATS & Recruitment Software
AI agents call hires_list_workflow_stages to retrieve information from 100Hires - AI ATS & Recruitment Software without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id | number | — | Filter stages by job ID (returns stages from the job's assigned workflow) |
company_id | number | — | Target company ID (uses default company when omitted) |
workflow_id | number | — | Filter stages by workflow ID (from hires_list_workflows) |
Parameters from the server's own tool schema.
Why hires_list_workflow_stages is rated Low
This tool retrieves and queries workflow stage data without creating, modifying, deleting, or executing any operations. It supports UI rendering and validation workflows, which are typical read operations. The lack of any action verbs (create, update, delete, execute) and the explicit mention of 'list' confirms this is a Read category tool.
From the tool's definition Tool name contains 'list' and description states 'List pipeline stages' — a retrieval operation with no side effects. Explicitly described as 'Useful for transition UIs and workflow validation', indicating read-only queries.
Attacks that exploit this kind of access
The rule that runs hires_list_workflow_stages 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_list_workflow_stages, this is the rule to start with:
hires_list_workflow_stages is read-only, so it stays allowed. 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_list_workflow_stages call is checked against it from then on.
Questions about hires_list_workflow_stages
List pipeline stages filtered by workflow or job. Useful for transition UIs and workflow validation. It is categorised as a Read tool in the 100Hires - AI ATS & Recruitment Software MCP Server, which means it retrieves data without modifying state.
hires_list_workflow_stages accepts 3 parameters: job_id, company_id, workflow_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_list_workflow_stages: 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_list_workflow_stages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hires_list_workflow_stages 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_list_workflow_stages. 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_list_workflow_stages 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