batch_continue · MCP GitHub Issue Priority Server MCP

WHAT IT DOES

What batch_continue does on MCP GitHub Issue Priority Server

AI agents invoke batch_continue to trigger actions in MCP GitHub Issue Priority Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why batch_continue needs a policy

This tool actively polls for PR merge status and advances the batch workflow to the next issue or signals completion. It triggers external operations (polling GitHub, advancing workflow state), making it Execute rather than Read. The blast radius is medium since misuse could cause unintended workflow progression or skip issues in the batch process.

From the tool's definition 'Continue batch implementation. Polls for PR merge, then returns next issue or completion.'

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_continue Rate-limited

batch_continue stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "batch_continue": {
      "limits": [
        {
          "counter": "batch_continue_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 batch_continue

What does the batch_continue tool do? +

Continue batch implementation. Polls for PR merge, then returns next issue or completion. It is categorised as a Execute tool in the MCP GitHub Issue Priority Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on batch_continue? +

Register the MCP GitHub Issue Priority Server MCP server in PolicyLayer and add a rule for batch_continue: 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 batch_continue? +

batch_continue is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit batch_continue? +

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

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

batch_continue 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.