list_associations
List Huly association definitions: class-level typed links that define which document classes may be related. Use this before create_relation to discover association IDs, source/target classes, and whether relation writes are supported.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-associations.md
What list_associations does on Huly
AI agents call list_associations 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_associations is rated Low
This tool retrieves metadata about typed links and associations without creating, modifying, or deleting anything. It is purely informational and used to discover schema before other operations. It fits the Read category as a data retrieval operation with no side effects.
From the tool's definition Tool description explicitly states 'List Huly association definitions' and 'discover association IDs, source/target classes' — retrieval and query operations with no side effects.
Attacks that exploit this kind of access
The rule that runs list_associations 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_associations, this is the rule to start with:
list_associations 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_associations call is checked against it from then on.
Questions about list_associations
List Huly association definitions: class-level typed links that define which document classes may be related. Use this before create_relation to discover association IDs, source/target classes, and whether relation writes are supported. 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_associations: 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_associations 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_associations 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_associations. 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_associations 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