set_chat_message_pinned
Idempotently pin or unpin a top-level message or thread reply located inside exactly one Huly channel or direct-message conversation. Provide
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/set-chat-message-pinned.md
What set_chat_message_pinned does on Huly
AI agents use set_chat_message_pinned 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_chat_message_pinned is rated Medium
This tool creates or modifies message metadata (pin status) reversibly. Users can toggle pins on and off, and the idempotent nature confirms no data is destroyed. This is a Write-category operation—data is changed but can be undone by unpinning. It does not read arbitrary data (Read), execute external code (Execute), permanently delete data (Destructive), or move financial value (Financial).
From the tool's definition Tool description states 'pin or unpin a top-level message' and is idempotent, indicating reversible modification of message state within a chat platform.
Attacks that exploit this kind of access
The rule that runs set_chat_message_pinned 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_chat_message_pinned, this is the rule to start with:
set_chat_message_pinned 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_chat_message_pinned call is checked against it from then on.
Questions about set_chat_message_pinned
Idempotently pin or unpin a top-level message or thread reply located inside exactly one Huly channel or direct-message conversation. Provide. 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_chat_message_pinned: 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_chat_message_pinned 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_chat_message_pinned 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_chat_message_pinned. 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_chat_message_pinned 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