add_object_collaborator
Subscribe a workspace member to object notifications by adding a core collaborator row. Member can be an account UUID, exact employee/person name, or email. Idempotent when already subscribed.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/add-object-collaborator.md
What add_object_collaborator does on Huly
AI agents use add_object_collaborator to create or update resources in Huly, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.
Why add_object_collaborator is rated Medium
This tool creates or modifies data (adding collaborator relationships) in a reversible manner. While it affects access and notifications, it does not execute arbitrary code, delete data, or move money. The idempotent nature confirms it is a write operation.
From the tool's definition Tool description states it will 'add a core collaborator row' and 'Subscribe a workspace member to object notifications', which are write operations that create or modify collaboration records.
Attacks that exploit this kind of access
The rule that runs add_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 add_object_collaborator, this is the rule to start with:
add_object_collaborator stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every add_object_collaborator call is checked against it from then on.
Questions about add_object_collaborator
Subscribe a workspace member to object notifications by adding a core collaborator row. Member can be an account UUID, exact employee/person name, or email. Idempotent when already subscribed. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Huly MCP server in PolicyLayer and add a rule for add_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.
add_object_collaborator is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_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.
This server
Across the catalogue