label_write
Perform write operations on repository labels. To set labels on issues, use the 'update_issue' tool.
This record as markdown: /tools/github/label-write.md
What label_write does on GitHub
AI agents use label_write to create or update resources in GitHub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Label name - required for all operations |
repo | string | — | Repository name |
color | string | — | Label color as 6-character hex code without '#' prefix (e.g., 'f29513'). Required for 'create', optional for 'update'. |
owner | string | — | Repository owner (username or organization name) |
method | string | — | Operation to perform: 'create', 'update', or 'delete' |
new_name | string | — | New name for the label (used only with 'update' method to rename) |
description | string | — | Label description text. Optional for 'create' and 'update'. |
Parameters from the server's own tool schema.
Why label_write is rated Medium
This tool creates or modifies repository labels, which are metadata on issues and pull requests. While reversible (labels can be removed/changed), it affects repository organization and issue categorization.
From the tool's definition Tool name 'label_write' explicitly states it performs 'write operations on repository labels'
Attacks that exploit this kind of access
The rule that runs label_write safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For label_write, this is the rule to start with:
label_write 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.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every label_write call is checked against it from then on.
Questions about label_write
Perform write operations on repository labels. To set labels on issues, use the 'update_issue' tool. 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.
label_write accepts 7 parameters: name, repo, color, owner, method, new_name, description. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for label_write: 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. Nothing to install.
label_write 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 label_write 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.
Set action: deny in the PolicyLayer policy for label_write. 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.
label_write is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue