delete_person
Permanently delete a person from Huly. This action cannot be undone.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/delete-person.md
What delete_person does on Huly
AI agents call delete_person 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.
Why delete_person is rated Critical
This tool irreversibly removes a person record from the system with no undo capability. While not financial or directly executing arbitrary code, it represents permanent data loss and violates the principle of reversibility. The blast radius is significant in a collaborative platform like Huly—deleting a person could cascade to affect projects, assignments, and organizational structure.
From the tool's definition Tool description explicitly states 'Permanently delete a person from Huly. This action cannot be undone.' The keywords 'Permanently delete' and 'cannot be undone' are characteristic of destructive operations.
Attacks that exploit this kind of access
The rule that runs delete_person 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_person, this is the rule to start with:
delete_person 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 Huly, apply this rule, and every delete_person call is checked against it from then on.
Questions about delete_person
Permanently delete a person from Huly. This action cannot be undone. 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.
Register the Huly MCP server in PolicyLayer and add a rule for delete_person: 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.
delete_person 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 delete_person 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 delete_person. 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.
delete_person 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.
More on Huly, and thousands of servers like it.
Across the catalogue