discussion-list
Lists GitHub Discussions for a repository via GraphQL. Returns structured list with discussion number, title, author, category, answered status, and comment count.
This record as markdown: /tools/io-github-dave-london-go/discussion-list.md
What discussion-list does on Go
AI agents call discussion-list to retrieve information from Go without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why discussion-list is rated Low
This tool queries and retrieves publicly available discussion metadata from GitHub via GraphQL. It performs no modifications, deletions, or execution of arbitrary code. The operation is read-only and returns structured data. The blast radius of misuse is minimal—an agent could at most retrieve discussion information they might not be authorized to see, but cannot modify or delete data.
From the tool's definition Tool description states it 'Lists GitHub Discussions for a repository' and 'Returns structured list with discussion number, title, author, category, answered status, and comment count.' This is purely a read/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs discussion-list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Go, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For discussion-list, this is the rule to start with:
discussion-list 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 Go, apply this rule, and every discussion-list call is checked against it from then on.
Questions about discussion-list
Lists GitHub Discussions for a repository via GraphQL. Returns structured list with discussion number, title, author, category, answered status, and comment count. It is categorised as a Read tool in the Go MCP Server, which means it retrieves data without modifying state.
Register the Go MCP server in PolicyLayer and add a rule for discussion-list: 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 Go. Nothing to install.
discussion-list 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 discussion-list 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 discussion-list. 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.
discussion-list is provided by the Go MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Go, and thousands of servers like it.
This server
Across the catalogue