list_object_collaborators
List notification collaborators on a Huly issue, document, or raw object. Prefer friendly targets: project+issueIdentifier for issues or teamspace+document for documents. Advanced callers may pass objectId+objectClass directly.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-object-collaborators.md
What list_object_collaborators does on Huly
AI agents call list_object_collaborators to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_object_collaborators is rated Low
This tool retrieves and lists existing collaborator information from Huly objects (issues, documents). It performs a read-only query operation with no capability to modify data, execute commands, or trigger external operations. The blast radius of misuse is minimal — an agent could enumerate collaborators but cannot change permissions, delete data, or cause harm. This is a straightforward Read category operation.
From the tool's definition Tool name is 'list_object_collaborators' and description states 'List notification collaborators' — retrieves/queries collaborator data with no modification, deletion, or execution of side effects.
Attacks that exploit this kind of access
The rule that runs list_object_collaborators 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 list_object_collaborators, this is the rule to start with:
list_object_collaborators is read-only, so it stays allowed. 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 list_object_collaborators call is checked against it from then on.
Questions about list_object_collaborators
List notification collaborators on a Huly issue, document, or raw object. Prefer friendly targets: project+issueIdentifier for issues or teamspace+document for documents. Advanced callers may pass objectId+objectClass directly. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for list_object_collaborators: 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.
list_object_collaborators is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_object_collaborators 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 list_object_collaborators. 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.
list_object_collaborators 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