get_discussion_comments
Get discussion comments
Part of the GitHub MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents call get_discussion_comments to retrieve information from GitHub without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions — but you may still want rate limits to control API costs.
WHY ENFORCE A POLICY ON GET_DISCUSSION_COMMENTS
Even though get_discussion_comments only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
RECOMMENDED POLICY
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_discussion_comments:
rules:
- action: allowSee the full GitHub policy for all 83 tools.
DETAILS
MORE GITHUB TOOLS
actions_get Read actions_list Read get_code_scanning_alert Read get_commit Read get_copilot_space Read get_dependabot_alert Read get_discussion Read get_file_contents Read SIMILAR READ TOOLS ON OTHER SERVERS
list_bases Airtable list_tables Airtable list_records Airtable get_record Airtable search_records Airtable search Amplitude RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the get_discussion_comments tool do?
Get discussion comments. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
How do I enforce a policy on get_discussion_comments?
Add a rule in your Intercept YAML policy under the tools section for get_discussion_comments. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the GitHub MCP server.
What risk level is get_discussion_comments?
get_discussion_comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Can I rate-limit get_discussion_comments?
Yes. Add a rate_limit block to the get_discussion_comments rule in your Intercept 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 get_discussion_comments completely?
Set action: deny in the Intercept policy for get_discussion_comments. 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 get_discussion_comments?
get_discussion_comments is provided by the GitHub MCP server (github/github-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON GITHUB
Open source. One binary. Zero dependencies.