list_active_threads
List a bounded set of active Discord threads visible inside one permitted guild. Optionally restrict to an exact permitted parent channel; forum and media posts are returned as public threads with applied tag IDs.
This record as markdown: /tools/app-lasers-guildcontrol-discord/list-active-threads.md
What list_active_threads does on GuildControl MCP
AI agents call list_active_threads 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_active_threads is rated Low
Queries and returns thread metadata with no ability to modify or delete data.
From the tool's definition List active threads, retrieves data, no side effects
Attacks that exploit this kind of access
The rule that runs list_active_threads 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_active_threads, this is the rule to start with:
list_active_threads 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_active_threads call is checked against it from then on.
Questions about list_active_threads
List a bounded set of active Discord threads visible inside one permitted guild. Optionally restrict to an exact permitted parent channel; forum and media posts are returned as public threads with applied tag IDs. 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_active_threads: 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_active_threads 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_active_threads 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_active_threads. 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_active_threads 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