issue-list

Lists issues with optional filters. Returns structured list with issue number, state, title, labels, assignees, author, creation date, and milestone.

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/issue-list.md

WHAT IT DOES

What issue-list does on Build

AI agents call issue-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 issue-list is rated Low

The tool only retrieves and returns issue data with no side effects. It is a pure read/query operation.

From the tool's definition 'Lists issues with optional filters. Returns structured list with issue number, state, title, labels, assignees, author, creation date, and milestone.'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs issue-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 issue-list, this is the rule to start with:

issue-list Allowed

issue-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": {
    "issue-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 issue-list call is checked against it from then on.

FAQ

Questions about issue-list

What does the issue-list tool do? +

Lists issues with optional filters. Returns structured list with issue number, state, title, labels, assignees, author, creation date, and milestone. 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 issue-list? +

Register the Build MCP server in PolicyLayer and add a rule for issue-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 issue-list? +

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

Can I rate-limit issue-list? +

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

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

issue-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 →