list_discussion_categories
AI agents call list_discussion_categories to retrieve information from GitHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_' prefix and naming pattern align with retrieval operations (list, get, fetch). Without destructive language or evidence of modification/deletion capabilities, this tool falls into the Read category. The low severity reflects that listing categories has minimal blast radius—it only retrieves metadata with no ability to modify, execute, or delete data.
From the tool's definition Tool name 'list_discussion_categories' indicates a retrieval operation that queries available discussion categories. No description provided, but the 'list_' prefix is a strong indicator of a read-only operation with no side effects.
Attacks that exploit this kind of access
list_discussion_categories. It is categorised as a Read tool in the GitHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for list_discussion_categories: 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 GitHub MCP Server. Nothing to install.
list_discussion_categories 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_discussion_categories 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_discussion_categories. 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_discussion_categories is provided by the GitHub MCP Server MCP server (software-engineer-mj/github-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →