delete_hr_request

Delete one exact HR request. Its comments and attachments are Huly-owned attached collections and follow the request deletion lifecycle.

SERVERHuly SOURCE@firfi/huly-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/delete-hr-request.md

WHAT IT DOES

What delete_hr_request does on Huly

AI agents call delete_hr_request to permanently remove resources in Huly, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_hr_request is rated Critical

Irreversibly deletes HR request and cascading data; cannot be undone.

From the tool's definition Delete one exact HR request. Its comments and attachments... follow the request deletion lifecycle.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_hr_request safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_hr_request, this is the rule to start with:

delete_hr_request Hidden

delete_hr_request is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_hr_request"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every delete_hr_request call is checked against it from then on.

FAQ

Questions about delete_hr_request

What does the delete_hr_request tool do? +

Delete one exact HR request. Its comments and attachments are Huly-owned attached collections and follow the request deletion lifecycle. It is categorised as a Destructive tool in the Huly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_hr_request? +

Register the Huly MCP server in PolicyLayer and add a rule for delete_hr_request: 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 Huly. Nothing to install.

What risk level is delete_hr_request? +

delete_hr_request is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_hr_request? +

Yes. Add a rate_limit block to the delete_hr_request 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.

How do I block delete_hr_request completely? +

Set action: deny in the PolicyLayer policy for delete_hr_request. 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.

What MCP server provides delete_hr_request? +

delete_hr_request is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 600 Huly tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →