set_class_collaborator_metadata
Create or replace direct core ClassCollaborators metadata for a class resolved by class ID, tail name, or label. fieldSelection supports all person-like fields, no fields, or exact property names validated against the class and its ancestors. Security propagation flags are normalized explicitly. ...
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/set-class-collaborator-metadata.md
What set_class_collaborator_metadata does on Huly
AI agents use set_class_collaborator_metadata 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 set_class_collaborator_metadata is rated Medium
This tool creates or replaces metadata for class collaborators, which modifies data reversibly. It does not delete data (so not Destructive), does not execute arbitrary code (so not Execute), and does not move money (so not Financial). The security guard mention suggests write protections are in place, making this a Write operation.
From the tool's definition Tool description explicitly states "Create or replace direct core ClassCollaborators metadata" which are write operations. The phrase "${SECURITY_WRITE_GUARD}" indicates this is a protected write operation.
Attacks that exploit this kind of access
The rule that runs set_class_collaborator_metadata 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 set_class_collaborator_metadata, this is the rule to start with:
set_class_collaborator_metadata 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 set_class_collaborator_metadata call is checked against it from then on.
Questions about set_class_collaborator_metadata
Create or replace direct core ClassCollaborators metadata for a class resolved by class ID, tail name, or label. fieldSelection supports all person-like fields, no fields, or exact property names validated against the class and its ancestors. Security propagation flags are normalized explicitly. ${SECURITY_WRITE_GUARD}. 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 set_class_collaborator_metadata: 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.
set_class_collaborator_metadata 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 set_class_collaborator_metadata 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 set_class_collaborator_metadata. 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.
set_class_collaborator_metadata 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