New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

set_conversation_closed

Set the authenticated user

SERVERHuly SOURCE@firfi/huly-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about set_conversation_closed

What does the set_conversation_closed tool do? +

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.

How do I enforce a policy on set_conversation_closed? +

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.

What risk level is set_conversation_closed? +

set_conversation_closed is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_conversation_closed? +

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.

How do I block set_conversation_closed completely? +

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.

What MCP server provides set_conversation_closed? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Huly's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.