list_pinned_chat_messages
List pinned top-level messages and pinned thread replies in exactly one Huly channel or direct-message conversation. Provide
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-pinned-chat-messages.md
What list_pinned_chat_messages does on Huly
AI agents call list_pinned_chat_messages 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_pinned_chat_messages is rated Low
This tool queries and retrieves pinned messages from a chat channel or DM conversation. It performs a read-only operation that does not create, modify, delete, or execute any actions. The verb 'list' is explicitly a Read category operation. Low severity due to limited blast radius—an AI agent misusing this would only retrieve chat messages already accessible within the specified channel, posing minimal risk.
From the tool's definition Tool name 'list_pinned_chat_messages' and description 'List pinned top-level messages and pinned thread replies' indicate retrieval of existing data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_pinned_chat_messages 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_pinned_chat_messages, this is the rule to start with:
list_pinned_chat_messages 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_pinned_chat_messages call is checked against it from then on.
Questions about list_pinned_chat_messages
List pinned top-level messages and pinned thread replies in exactly one Huly channel or direct-message conversation. Provide. 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_pinned_chat_messages: 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_pinned_chat_messages 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_pinned_chat_messages 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_pinned_chat_messages. 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_pinned_chat_messages 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