Update one or more fields of an existing MantisBT issue using a partial PATCH. The "fields" object accepts any combination of: - summary (string) - description (string) - steps_to_reproduce (string) - additional_information (string) - status: { name: "new"|"feedback"|"acknowledged"|"confirmed"|"a...
AI agents use update_issue to create or update resources in MantisBT MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MantisBT MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | integer | Yes | Numeric issue ID to update |
note | string | — | Optional note text appended after a successful update (e.g. reason for a status change). Replaces a separate add_note call. |
fields | object | Yes | Fields to update (partial update — only provided fields are changed; unknown keys are rejected) |
dry_run | boolean | — | If true, return the patch payload that would be sent without actually updating the issue. Useful for previewing changes before committing them. |
note_view_state | string | — | Visibility of the appended note: "public" (default) or "private". Only used when "note" is set. |
Parameters from the server's own tool schema.
This tool creates or modifies data reversibly by updating issue fields in MantisBT. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). The modifications are reversible—users can update fields again to restore previous values.
From the tool's definition Tool description explicitly states 'Update one or more fields of an existing MantisBT issue using a partial PATCH.' The fields object accepts modifications to summary, description, status, resolution, handler assignment, priority, severity, and category.
Risk signalsHigh parameter count (25 properties)
Attacks that exploit this kind of access
Update one or more fields of an existing MantisBT issue using a partial PATCH. The "fields" object accepts any combination of: - summary (string) - description (string) - steps_to_reproduce (string) - additional_information (string) - status: { name: "new"|"feedback"|"acknowledged"|"confirmed"|"assigned"|"resolved"|"closed" } - resolution: { id: 20 } (20 = fixed/resolved) - handler: { id: <user_id> } or { name: "<username>" } - priority: { name: "<priority_name>" } - severity: { name: "<severity_name>" } - reproducibility: { name: "<reproducibility_name>" } - category: { name: "<category_name>" } - version: { name: "<version_name>" } (affected version) - target_version: { name: "<version_name>" } - fixed_in_version: { name: "<version_name>" } - view_state: { name: "public"|"private" } - custom_fields: [{field: {id|name}, value: "<string>"}] (only the listed custom fields are changed, others stay untouched; use get_issue_fields to discover fields) Important: when resolving an issue, always set BOTH status and resolution to avoid leaving resolution as "open". Use the optional "note" parameter to append a note in the same call (e.g. the reason for a status change) — no separate add_note call needed. For a note without field changes use add_note. It is categorised as a Write tool in the MantisBT MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_issue accepts 5 parameters: id, note, fields, dry_run, note_view_state. Required: id, fields. The full parameter table on this page comes from the server's own tool schema.
Register the MantisBT MCP Server MCP server in PolicyLayer and add a rule for update_issue: 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 MantisBT MCP Server. Nothing to install.
update_issue 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 update_issue 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 update_issue. 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.
update_issue is provided by the MantisBT MCP Server MCP server (@dpesch/mantisbt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →