select_next_issue · MCP GitHub Issue Priority Server MCP

WHAT IT DOES

What select_next_issue does on MCP GitHub Issue Priority Server

AI agents use select_next_issue to create or update resources in MCP GitHub Issue Priority Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP GitHub Issue Priority Server environment.

WHY IT NEEDS A POLICY

Why select_next_issue needs a policy

This tool both reads (selects the highest-priority issue) and writes (locks it, implying a state change on the issue record). Locking is a reversible write operation that modifies the issue's state in the system. Since Write is more severe than Read, it is classified as Write. The blast radius is medium — misuse could lock issues incorrectly and block other workflows, but it is reversible.

From the tool's definition Select and lock the highest-priority issue from the backlog

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

select_next_issue Rate-limited

select_next_issue stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "select_next_issue": {
      "limits": [
        {
          "counter": "select_next_issue_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP GitHub Issue Priority Server, so you can run agents against it safely.

FAQ

Questions about select_next_issue

What does the select_next_issue tool do? +

Select and lock the highest-priority issue from the backlog. It is categorised as a Write tool in the MCP GitHub Issue Priority Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on select_next_issue? +

Register the MCP GitHub Issue Priority Server MCP server in PolicyLayer and add a rule for select_next_issue: 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 MCP GitHub Issue Priority Server. Nothing to install.

What risk level is select_next_issue? +

select_next_issue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit select_next_issue? +

Yes. Add a rate_limit block to the select_next_issue 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 select_next_issue completely? +

Set action: deny in the PolicyLayer policy for select_next_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.

What MCP server provides select_next_issue? +

select_next_issue is provided by the MCP GitHub Issue Priority Server MCP server (steiner385/mcp-git-issue-priority). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.