issue-update

Updates issue metadata (title, body, labels, assignees, milestone, projects).

SERVERBuild SOURCEDave-London/Pare

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-build/issue-update.md

WHAT IT DOES

What issue-update does on Build

AI agents use issue-update 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.

RISK

Why issue-update is rated Medium

This tool creates or modifies data reversibly. It updates issue metadata fields without deleting them, making it a Write operation. Severity is medium because misuse could alter important project tracking information, but changes are reversible and don't involve financial transactions, code execution, or data deletion.

From the tool's definition Tool name 'issue-update' and description states it 'Updates issue metadata (title, body, labels, assignees, milestone, projects)' — modifies existing issue data through update operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

issue-update Rate-limited

issue-update 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "issue-update": {
      "limits": [
        {
          "counter": "issue-update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about issue-update

What does the issue-update tool do? +

Updates issue metadata (title, body, labels, assignees, milestone, projects). 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.

How do I enforce a policy on issue-update? +

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

issue-update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit issue-update? +

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

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

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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →