discussion-list

Lists GitHub Discussions for a repository via GraphQL. Returns structured list with discussion number, title, author, category, answered status, and comment count.

SERVERLint SOURCEDave-London/Pare

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/io-github-dave-london-lint/discussion-list.md

WHAT IT DOES

What discussion-list does on Lint

AI agents call discussion-list to retrieve information from Lint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why discussion-list is rated Low

This is a pure read operation that queries GitHub's GraphQL API to fetch discussion metadata. It has no ability to create, modify, delete, or execute any actions. The tool only retrieves publicly available discussion information in a structured format, making it a low-severity Read category with high confidence.

From the tool's definition The tool 'Lists GitHub Discussions for a repository' via GraphQL—it retrieves and returns structured data (discussion number, title, author, category, answered status, comment count) with no modifications or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs discussion-list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Lint, 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 Allowed

discussion-list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "discussion-list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Lint, apply this rule, and every discussion-list call is checked against it from then on.

FAQ

Questions about discussion-list

What does the discussion-list tool do? +

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 Lint MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on discussion-list? +

Register the Lint 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 Lint. Nothing to install.

What risk level is discussion-list? +

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

Can I rate-limit discussion-list? +

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.

How do I block discussion-list completely? +

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.

What MCP server provides discussion-list? +

discussion-list is provided by the Lint MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Lint, and thousands of servers like it.

This server

All 202 Lint tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →