This record as markdown: /tools/io-github-dearlordylord-huly-mcp/remove-organization-member.md
What remove_organization_member does on Huly
AI agents call remove_organization_member 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 remove_organization_member is rated Critical
This tool permanently removes a person's link to an organization, which cannot be undone through normal application workflows without explicit re-addition by an administrator. While not directly destructive to data records themselves, the action irreversibly severs organizational membership and associated permissions/access.
From the tool's definition Tool performs 'Unlink a person from an organization' - a membership removal action that severs organizational relationships and is irreversible without administrative re-linking; the 'remove' action indicates deletion/unlinking of organizational associations.
Attacks that exploit this kind of access
The rule that runs remove_organization_member 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 remove_organization_member, this is the rule to start with:
remove_organization_member 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 remove_organization_member call is checked against it from then on.
Questions about remove_organization_member
Unlink a person from an organization. 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 remove_organization_member: 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.
remove_organization_member 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 remove_organization_member 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 remove_organization_member. 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.
remove_organization_member 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