add_labels_to_issue · GitHub Project MCP Server MCP

WHAT IT DOES

What add_labels_to_issue does on GitHub Project MCP Server

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

WHY IT NEEDS A POLICY

Why add_labels_to_issue needs a policy

Adding labels to an issue is a reversible modification operation—labels can be added or removed without permanently destroying data or affecting other systems. This constitutes a Write operation rather than Read (which only retrieves data) or Destructive (which cannot be undone).

From the tool's definition Tool description states 'Add labels to an issue', which modifies issue metadata. The server description confirms it supports 'managing labels' as part of issue management operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_labels_to_issue Rate-limited

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

FAQ

Questions about add_labels_to_issue

What does the add_labels_to_issue tool do? +

Add labels to an issue. It is categorised as a Write tool in the GitHub Project 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 add_labels_to_issue? +

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

What risk level is add_labels_to_issue? +

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

Can I rate-limit add_labels_to_issue? +

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

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

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