hires_list_application_stage_history

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

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-100hires-100hires/hires-list-application-stage-history.md

WHAT IT DOES

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

AI agents call hires_list_application_stage_history 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	Application ID.

Parameters from the server's own tool schema.

RISK

Why hires_list_application_stage_history is rated Low

This tool queries and returns application stage history data without creating, modifying, deleting, or executing operations. It is purely informational retrieval with no side effects on the ATS system. Low severity due to minimal blast radius — misuse returns historical records rather than causing operational harm.

From the tool's definition Tool name contains 'list' and description states 'Get the full chronological stage transition history' — retrieves historical data with no modifications.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hires_list_application_stage_history Allowed

hires_list_application_stage_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hires_list_application_stage_history": {}
  }
}

ALLOW ONLY 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_list_application_stage_history call is checked against it from then on.

FAQ

Questions about hires_list_application_stage_history

What does the hires_list_application_stage_history tool do? +

Get the full chronological stage transition history for an application, including the initial assignment. Each entry has from_stage_id/name, to_stage_id/name, moved_at (Unix seconds), moved_by_type (system, user, automation), moved_by_user_id, and source (what caused the transition, e.g. 'apply:indeed', 'form_watcher', 'user'; null for historical records). Use this for funnel analysis, attribution reports, and time-in-stage reports instead of paginating through /candidates/{id}/activities when only stage data is needed. It is categorised as a Read tool in the 100Hires - AI ATS & Recruitment Software MCP Server, which means it retrieves data without modifying state.

What parameters does hires_list_application_stage_history accept? +

hires_list_application_stage_history accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hires_list_application_stage_history? +

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

hires_list_application_stage_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hires_list_application_stage_history? +

Yes. Add a rate_limit block to the hires_list_application_stage_history 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_list_application_stage_history completely? +

Set action: deny in the PolicyLayer policy for hires_list_application_stage_history. 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_list_application_stage_history? +

hires_list_application_stage_history 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →