Triage an issue by capturing a focused triage rationale and optionally applying metadata (labels, issue type, and issue fields) in a single operation. Use this tool when: - You are triaging a newly opened or untriaged issue for maintainers - You need to categorize the issue (type) and suggest/app...
Single-target operation
Part of the GitHub MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use triage_issue to create or modify resources in GitHub. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call triage_issue repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach GitHub.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
triage_issue:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full GitHub policy for all 86 tools.
Agents calling write-class tools like triage_issue have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Triage an issue by capturing a focused triage rationale and optionally applying metadata (labels, issue type, and issue fields) in a single operation. Use this tool when: - You are triaging a newly opened or untriaged issue for maintainers - You need to categorize the issue (type) and suggest/apply relevant labels - You want to record a brief, structured triage report Do not use this tool when: - The user is asking a general product question unrelated to triaging a specific issue triage_rationale should be concise markdown aimed at maintainers (not the issue author); it should contain: - Summary of the issue - Analysis of the problem or request - Suggested next steps or actions.. It is categorised as a Write tool in the GitHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for triage_issue. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the GitHub MCP server.
triage_issue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the triage_issue 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.
Set action: deny in the Intercept policy for triage_issue. 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.
triage_issue 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.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept