remove_object_collaborator
Unsubscribe a workspace member from object notifications by removing its collaborator row. Member can be an account UUID, exact employee/person name, or email. Idempotent when already absent.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/remove-object-collaborator.md
What remove_object_collaborator does on Huly
AI agents call remove_object_collaborator 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_object_collaborator is rated Critical
The tool removes a collaborator row, which is a deletion operation. While it's described as idempotent and doesn't delete primary content, removing a collaborator row is not easily reversible without knowing the previous state. The blast radius is medium since it affects notification subscriptions for workspace members, potentially causing them to miss important updates.
From the tool's definition removing its collaborator row
Attacks that exploit this kind of access
The rule that runs remove_object_collaborator 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_object_collaborator, this is the rule to start with:
remove_object_collaborator 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_object_collaborator call is checked against it from then on.
Questions about remove_object_collaborator
Unsubscribe a workspace member from object notifications by removing its collaborator row. Member can be an account UUID, exact employee/person name, or email. Idempotent when already absent. 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_object_collaborator: 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_object_collaborator 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_object_collaborator 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_object_collaborator. 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_object_collaborator 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