label-list
Lists repository labels. Returns structured data with label name, description, color, and default status.
This record as markdown: /tools/io-github-dave-london-git/label-list.md
What label-list does on Git
AI agents call label-list to retrieve information from Git without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why label-list is rated Low
This tool retrieves and presents existing label information from a repository. It performs a read-only query with no capability to create, modify, delete, or execute operations. The data returned (label name, description, color, default status) is metadata that cannot cause harm if exposed to an AI agent.
From the tool's definition Tool name 'label-list' and description 'Lists repository labels' indicate a query operation that retrieves label metadata without modification. The description confirms it 'Returns structured data' with no side effects mentioned.
Attacks that exploit this kind of access
The rule that runs label-list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Git, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every label-list call is checked against it from then on.
Questions about label-list
Lists repository labels. Returns structured data with label name, description, color, and default status. It is categorised as a Read tool in the Git MCP Server, which means it retrieves data without modifying state.
Register the Git 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 Git. Nothing to install.
label-list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
label-list is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Git, and thousands of servers like it.
This server
Across the catalogue