list_message_replies
Inspect direct replies to one exact Discord message by scanning one bounded page after a caller-held exact cursor. Returns a privacy-minimized source and only strict same-channel replies in ascending order plus honest scan coverage and the next cursor; non-replies advance coverage but are omitted...
This record as markdown: /tools/app-lasers-guildcontrol-discord/list-message-replies.md
What list_message_replies does on GuildControl MCP
AI agents call list_message_replies to retrieve information from GuildControl MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_message_replies is rated Low
Retrieves and queries message replies without side effects, modifications, or persistence.
From the tool's definition Inspect direct replies, scanning one bounded page, returns privacy-minimized source.
Attacks that exploit this kind of access
The rule that runs list_message_replies safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GuildControl MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_message_replies, this is the rule to start with:
list_message_replies 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 GuildControl MCP, apply this rule, and every list_message_replies call is checked against it from then on.
Questions about list_message_replies
Inspect direct replies to one exact Discord message by scanning one bounded page after a caller-held exact cursor. Returns a privacy-minimized source and only strict same-channel replies in ascending order plus honest scan coverage and the next cursor; non-replies advance coverage but are omitted, profile and rich payload fields are withheld, and nothing is persisted. It is categorised as a Read tool in the GuildControl MCP MCP Server, which means it retrieves data without modifying state.
Register the GuildControl MCP server in PolicyLayer and add a rule for list_message_replies: 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 GuildControl MCP. Nothing to install.
list_message_replies 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_message_replies 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_message_replies. 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_message_replies is provided by the GuildControl MCP server (guildctl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GuildControl, and thousands of servers like it.
This server
Across the catalogue