anti_demissions_hr
Bouclier anti-démissions — Gapup agent-payable C-suite expertise (COO). Returns a structured, audited deliverable. Reference case: Buffer Inc — détection des at-risk parmi 80 FTEs (Q1 2026). Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-gapup-mcp/anti-demissions-hr.md
What anti_demissions_hr does on Gapup Mcp
AI agents use anti_demissions_hr to commit financial operations through Gapup Mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
focus | string | — | |
company | object | Yes | |
signals | object | Yes | |
employees | array | Yes |
Parameters from the server's own tool schema.
Why anti_demissions_hr is rated Critical
The server explicitly states '271 agent-payable tools' with 'x402 per-call' billing. Every invocation of this tool triggers a micropayment/financial obligation. The tool itself appears to be an HR analytics/retention advisory service (identifying at-risk employees), which would otherwise be classified as Read/Execute, but the per-call payment commitment elevates it to Financial category per the severity hierarchy…
From the tool's definition Gapup agent-payable C-suite expertise (COO) ... x402 per-call (from server description); each invocation incurs a direct per-call financial charge via x402 protocol
Risk signalsHigh parameter count (24 properties)
Attacks that exploit this kind of access
The rule that runs anti_demissions_hr safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For anti_demissions_hr, this is the rule to start with:
Any call to anti_demissions_hr is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gapup Mcp, apply this rule, and every anti_demissions_hr call is checked against it from then on.
Questions about anti_demissions_hr
Bouclier anti-démissions — Gapup agent-payable C-suite expertise (COO). Returns a structured, audited deliverable. Reference case: Buffer Inc — détection des at-risk parmi 80 FTEs (Q1 2026). Inputs are validated server-side — send the documented case fields. It is categorised as a Financial tool in the Gapup Mcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
anti_demissions_hr accepts 5 parameters: async, focus, company, signals, employees. Required: company, signals, employees. The full parameter table on this page comes from the server's own tool schema.
Register the Gapup MCP server in PolicyLayer and add a rule for anti_demissions_hr: 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 Gapup Mcp. Nothing to install.
anti_demissions_hr is a Financial 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 anti_demissions_hr 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 anti_demissions_hr. 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.
anti_demissions_hr is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gapup, and thousands of servers like it.
Across the catalogue