remove_organization_member

Unlink a person from an organization

SERVERHuly SOURCEdugynoo/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/dugynoo-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

Removing a member from an organization is irreversible without explicit administrative action to re-add them. This constitutes a destructive operation affecting organizational structure and access. While not deleting data, it permanently severs a person-organization relationship and typically revokes access rights, making it more severe than a simple Write operation.

From the tool's definition Tool name is 'remove_organization_member' and description states 'Unlink a person from an organization'. This action removes an organizational relationship that cannot be easily reversed without manual intervention by an administrator.

Questions about remove_organization_member

What does the remove_organization_member tool do? +

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.

How do I enforce a policy on remove_organization_member? +

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.

What risk level is remove_organization_member? +

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.

Can I rate-limit remove_organization_member? +

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.

How do I block remove_organization_member completely? +

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.

What MCP server provides remove_organization_member? +

remove_organization_member 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Huly's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.