delete_organization
Permanently delete an organization identified by ID or exact name when that name is unique. Use with care - this cannot be undone. Useful for cleaning up duplicate organizations after merging their data elsewhere. If multiple organizations share the same name, use the organization ID.
This record as markdown: /tools/dugynoo-huly-mcp/delete-organization.md
What delete_organization does on Huly
AI agents call delete_organization 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_organization is rated Critical
This tool irreversibly deletes entire organization entities and all associated data. Per the classification rules, destructive operations (delete) that cannot be undone take precedence over other categories.
From the tool's definition Tool name is 'delete_organization' and description explicitly states 'Permanently delete an organization' and 'this cannot be undone', indicating irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs delete_organization 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_organization, this is the rule to start with:
delete_organization 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_organization call is checked against it from then on.
Questions about delete_organization
Permanently delete an organization identified by ID or exact name when that name is unique. Use with care - this cannot be undone. Useful for cleaning up duplicate organizations after merging their data elsewhere. If multiple organizations share the same name, use the organization ID. 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_organization: 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_organization 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_organization 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_organization. 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_organization is provided by the Huly MCP server (dugynoo/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