This record as markdown: /tools/io-github-dearlordylord-huly-mcp/set-conversation-closed.md
What set_conversation_closed does on Huly
AI agents use set_conversation_closed 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_conversation_closed is rated Medium
The tool's name strongly suggests it changes the closed/open status of a conversation, which is a reversible modification (conversations can be reopened). This is a Write operation. While the description is unhelpfully generic, the function name is the primary indicator. Severity is medium because closing a conversation could disrupt communication workflows, but the effect is reversible.
From the tool's definition Tool name 'set_conversation_closed' indicates it modifies state (sets a closed status on a conversation). The description 'Set the authenticated user' is vague and appears incomplete or inconsistent with the name.
Attacks that exploit this kind of access
The rule that runs set_conversation_closed 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_conversation_closed, this is the rule to start with:
set_conversation_closed 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_conversation_closed call is checked against it from then on.
Questions about set_conversation_closed
Set the authenticated user. 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_conversation_closed: 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_conversation_closed 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_conversation_closed 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_conversation_closed. 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_conversation_closed 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