batch_add_labels · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What batch_add_labels does on GitHub MCP Server

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

WHY IT NEEDS A POLICY

Why batch_add_labels needs a policy

This tool modifies issue metadata by adding labels to multiple issues. While the operation affects multiple resources (batch operation), the changes are reversible—labels can be removed. This is a Write operation rather than Execute because it performs a specific metadata update rather than arbitrary code execution.

From the tool's definition Tool description states labels are 'ADDED' to multiple issues, indicating a reversible modification operation that changes issue metadata without deletion or financial impact.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_add_labels Rate-limited

batch_add_labels 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": {
    "batch_add_labels": {
      "limits": [
        {
          "counter": "batch_add_labels_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 GitHub MCP Server, so you can run agents against it safely.

FAQ

Questions about batch_add_labels

What does the batch_add_labels tool do? +

Add labels to multiple issues in parallel. Labels are ADDED (not replaced). It is categorised as a Write tool in the GitHub MCP 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 batch_add_labels? +

Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for batch_add_labels: 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.

What risk level is batch_add_labels? +

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

Can I rate-limit batch_add_labels? +

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

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

batch_add_labels is provided by the GitHub MCP Server MCP server (rriesco/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.