label-list

Lists repository labels. Returns structured data with label name, description, color, and default status.

SERVERBuild SOURCEDave-London/Pare

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-build/label-list.md

WHAT IT DOES

What label-list does on Build

AI agents call label-list to retrieve information from Build without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why label-list is rated Low

This tool retrieves metadata about repository labels (name, description, color, default status) without performing any side effects. It is a pure read operation that queries and returns existing data structure. No data is created, modified, deleted, or executed.

From the tool's definition Tool name 'label-list' and description explicitly states it 'Lists repository labels' and 'Returns structured data'. The verb 'Lists' combined with 'Returns' indicates data retrieval with no modification, deletion, or execution of code.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs label-list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Build, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For label-list, this is the rule to start with:

label-list Allowed

label-list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "label-list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Build, apply this rule, and every label-list call is checked against it from then on.

FAQ

Questions about label-list

What does the label-list tool do? +

Lists repository labels. Returns structured data with label name, description, color, and default status. It is categorised as a Read tool in the Build MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on label-list? +

Register the Build MCP server in PolicyLayer and add a rule for label-list: 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 Build. Nothing to install.

What risk level is label-list? +

label-list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit label-list? +

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

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

label-list is provided by the Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Build, and thousands of servers like it.

This server

All 202 Build tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →