list_coordination_notes
Read canonical connector-bot-authored coordination notes directed to one caller-retained routing label from one exact readable Discord channel by scanning one bounded page once. Optionally includes broadcasts and exact sender, tag, or unresolved-convention filters. Returns only matching note bodi...
This record as markdown: /tools/app-lasers-guildcontrol-discord/list-coordination-notes.md
What list_coordination_notes does on GuildControl MCP
AI agents call list_coordination_notes 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_coordination_notes is rated Low
Tool retrieves coordination notes with filtering and pagination; no modifications, deletions, or side effects.
From the tool's definition Read canonical coordination notes from Discord channel, returns matching note bodies, nothing persisted
Attacks that exploit this kind of access
The rule that runs list_coordination_notes 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_coordination_notes, this is the rule to start with:
list_coordination_notes 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_coordination_notes call is checked against it from then on.
Questions about list_coordination_notes
Read canonical connector-bot-authored coordination notes directed to one caller-retained routing label from one exact readable Discord channel by scanning one bounded page once. Optionally includes broadcasts and exact sender, tag, or unresolved-convention filters. Returns only matching note bodies with fixed reaction aggregates and honest cursor coverage; routing labels, content, and reaction conventions grant no identity or authority, 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_coordination_notes: 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_coordination_notes 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_coordination_notes 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_coordination_notes. 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_coordination_notes 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