issue-create
Creates a new issue. Returns structured data with issue number, URL, and labels applied.
This record as markdown: /tools/io-github-dave-london-build/issue-create.md
What issue-create does on Build
AI agents use issue-create to create or update resources in Build, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Build environment.
Why issue-create is rated Medium
This tool creates new issues in what is likely a build/CI system or issue tracking system. Issue creation is a reversible write operation—issues can be edited, closed, or deleted later. The blast radius is moderate: an agent could spam issues, pollute tracking systems, or create misleading build diagnostics, but this is recoverable and does not execute arbitrary code or delete data irreversibly.
From the tool's definition Tool name 'issue-create' and description 'Creates a new issue' indicate the tool creates new data. Returns structured data with issue number, URL, and labels applied, confirming data creation.
Attacks that exploit this kind of access
The rule that runs issue-create 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-create, this is the rule to start with:
issue-create 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 Build, apply this rule, and every issue-create call is checked against it from then on.
Questions about issue-create
Creates a new issue. Returns structured data with issue number, URL, and labels applied. It is categorised as a Write tool in the Build MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Build MCP server in PolicyLayer and add a rule for issue-create: 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.
issue-create 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 issue-create 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 issue-create. 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.
issue-create 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.
More on Build, and thousands of servers like it.
This server
Across the catalogue