New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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...

SERVERGuildControl MCP SOURCEguildctl
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about list_coordination_notes

What does the list_coordination_notes tool do? +

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.

How do I enforce a policy on list_coordination_notes? +

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.

What risk level is list_coordination_notes? +

list_coordination_notes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_coordination_notes? +

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.

How do I block list_coordination_notes completely? +

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.

What MCP server provides list_coordination_notes? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GuildControl's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.