hires_get_notification_message
Get a notification email message (e.g. rejection email) by ID. Returns subject, body, sender, recipient, and schedule metadata. Use candidate messages list to discover notification message IDs.
This record as markdown: /tools/com-100hires-100hires/hires-get-notification-message.md
What hires_get_notification_message does on 100Hires - AI ATS & Recruitment Software
AI agents call hires_get_notification_message 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 | integer | Yes | Notification email message ID. |
Parameters from the server's own tool schema.
Why hires_get_notification_message is rated Low
This tool retrieves pre-existing notification email records by ID and returns their metadata. It performs a query operation without modifying, deleting, or executing any action. The data returned (subject, body, sender, recipient, schedule metadata) is informational only. No candidate records are altered, no messages are sent, and no state changes occur.
From the tool's definition Tool description states 'Get a notification email message... Returns subject, body, sender, recipient, and schedule metadata.' The verb 'Get' and the read-only nature of retrieving stored notification data indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs hires_get_notification_message 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_notification_message, this is the rule to start with:
hires_get_notification_message 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_notification_message call is checked against it from then on.
Questions about hires_get_notification_message
Get a notification email message (e.g. rejection email) by ID. Returns subject, body, sender, recipient, and schedule metadata. Use candidate messages list to discover notification message IDs. 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_notification_message accepts 1 parameter: 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_notification_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 - AI ATS & Recruitment Software. Nothing to install.
hires_get_notification_message 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_notification_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_get_notification_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_get_notification_message 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