hires_cancel_all_notification_messages
Cancel all scheduled notification emails for a candidate. Already sent notifications are not affected. Returns success even if no scheduled notifications exist.
This record as markdown: /tools/100hires-mcp-server/hires-cancel-all-notification-messages.md
What hires_cancel_all_notification_messages does on 100Hires MCP Server
AI agents call hires_cancel_all_notification_messages to permanently remove resources in 100Hires MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why hires_cancel_all_notification_messages is rated Critical
Cancelling all scheduled notification messages is an irreversible bulk action — once cancelled, those scheduled notifications are gone and cannot be recovered or rescheduled automatically. This affects all pending communications for a candidate, which could disrupt hiring workflows. The irreversibility and broad scope (all scheduled notifications) places this in the Destructive category with high severity.
From the tool's definition Cancel all scheduled notification emails for a candidate. Already sent notifications are not affected.
Attacks that exploit this kind of access
The rule that runs hires_cancel_all_notification_messages 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_cancel_all_notification_messages, this is the rule to start with:
hires_cancel_all_notification_messages is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 100Hires MCP Server, apply this rule, and every hires_cancel_all_notification_messages call is checked against it from then on.
Questions about hires_cancel_all_notification_messages
Cancel all scheduled notification emails for a candidate. Already sent notifications are not affected. Returns success even if no scheduled notifications exist. It is categorised as a Destructive tool in the 100Hires MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 100Hires MCP Server MCP server in PolicyLayer and add a rule for hires_cancel_all_notification_messages: 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_cancel_all_notification_messages is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the hires_cancel_all_notification_messages 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_cancel_all_notification_messages. 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_cancel_all_notification_messages 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.
Across the catalogue