Add labels to an existing issue.
AI agents use add_labels to create or update resources in Mcp Github Pm — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Github Pm environment.
This tool modifies issue state by attaching labels, which is a non-destructive write operation. Labels can be easily removed, making this a standard metadata update. The blast radius is minimal since label changes do not affect core issue data, financial systems, or enable code execution. Severity is 'low' because misuse would result in cosmetic/organizational issues rather than data loss or system compromise.
From the tool's definition Tool name 'add_labels' and description 'Add labels to an existing issue' indicate modification of issue metadata. Labels are reversible attributes that can be added or removed without data loss or destructive consequences.
Attacks that exploit this kind of access
Add labels to an existing issue. It is categorised as a Write tool in the Mcp Github Pm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Github Pm MCP server in PolicyLayer and add a rule for 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 Mcp Github Pm. Nothing to install.
add_labels 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 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.
Set action: deny in the PolicyLayer policy for 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.
add_labels is provided by the Mcp Github Pm MCP server (lordbasilaiassistant-sudo/mcp-github-pm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →