hires_get_workflow_stages
Get stages for a specific workflow by ID. Equivalent to hires_list_workflow_stages with workflow_id filter.
This record as markdown: /tools/com-100hires-100hires/hires-get-workflow-stages.md
What hires_get_workflow_stages does on 100Hires - AI ATS & Recruitment Software
AI agents call hires_get_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 |
|---|---|---|---|
id | number | Yes | Workflow ID |
company_id | number | — | Target company ID (uses default company when omitted) |
Parameters from the server's own tool schema.
Why hires_get_workflow_stages is rated Low
This tool retrieves workflow stage metadata by querying for a specific workflow ID. It performs a read-only query operation without modifying, deleting, executing external code, or affecting financial data. The low severity reflects that workflow stage information is typically non-sensitive configuration data used for viewing recruitment pipeline structure.
From the tool's definition Tool name is 'hires_get_workflow_stages' and description explicitly states 'Get stages for a specific workflow by ID.' The verb 'Get' and the functional equivalence to 'hires_list_workflow_stages' with a filter indicate a retrieval operation with no side…
Attacks that exploit this kind of access
The rule that runs hires_get_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_get_workflow_stages, this is the rule to start with:
hires_get_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_get_workflow_stages call is checked against it from then on.
Questions about hires_get_workflow_stages
Get stages for a specific workflow by ID. Equivalent to hires_list_workflow_stages with workflow_id filter. 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_get_workflow_stages accepts 2 parameters: id, company_id. 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_get_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_get_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_get_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_get_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_get_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