hires_send_candidate_message
Schedule an email message to a candidate. If scheduled_at is omitted, the message is scheduled for 15 minutes after creation.
This record as markdown: /tools/100hires-mcp-server/hires-send-candidate-message.md
What hires_send_candidate_message does on 100Hires MCP Server
AI agents use hires_send_candidate_message to create or update resources in 100Hires MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 100Hires MCP Server environment.
Why hires_send_candidate_message is rated Medium
This tool creates and schedules a new email message, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. While it affects candidate communications (potentially affecting recruitment outcomes), the action is reversible—messages can be unsent or candidates can opt out.
From the tool's definition "Schedule an email message to a candidate" — creates a new message record with scheduling, modifying the state of candidate communications.
Attacks that exploit this kind of access
The rule that runs hires_send_candidate_message 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_send_candidate_message, this is the rule to start with:
hires_send_candidate_message 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 MCP Server, apply this rule, and every hires_send_candidate_message call is checked against it from then on.
Questions about hires_send_candidate_message
Schedule an email message to a candidate. If scheduled_at is omitted, the message is scheduled for 15 minutes after creation. It is categorised as a Write tool in the 100Hires MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 100Hires MCP Server MCP server in PolicyLayer and add a rule for hires_send_candidate_message: 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_send_candidate_message 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_send_candidate_message 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_send_candidate_message. 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_send_candidate_message 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