hires_list_candidate_activities
List timeline activities for a candidate (comments, stage moves, AI responses, etc.). Supports filtering by event type.
This record as markdown: /tools/100hires-mcp-server/hires-list-candidate-activities.md
What hires_list_candidate_activities does on 100Hires MCP Server
AI agents call hires_list_candidate_activities to retrieve information from 100Hires MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why hires_list_candidate_activities is rated Low
This tool retrieves historical activity data (comments, stage moves, AI responses) for a candidate in read-only fashion. It has no side effects on the candidate record or system state. Even in the context of an ATS with access to sensitive recruitment data, listing activities is a fundamental read operation with minimal blast radius—it cannot modify candidates, applications, jobs, or financial records.
From the tool's definition Tool lists timeline activities and comments for a candidate with optional filtering; the description explicitly uses verbs 'list' and 'supports filtering', indicating retrieval of existing data without modification.
Attacks that exploit this kind of access
The rule that runs hires_list_candidate_activities 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_list_candidate_activities, this is the rule to start with:
hires_list_candidate_activities 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 MCP Server, apply this rule, and every hires_list_candidate_activities call is checked against it from then on.
Questions about hires_list_candidate_activities
List timeline activities for a candidate (comments, stage moves, AI responses, etc.). Supports filtering by event type. It is categorised as a Read tool in the 100Hires MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 100Hires MCP Server MCP server in PolicyLayer and add a rule for hires_list_candidate_activities: 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_list_candidate_activities 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_candidate_activities 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_candidate_activities. 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_candidate_activities 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