Add a note (comment) to an existing MantisBT issue. Returns the created note object including id, created_at, reporter, text, view_state, and a view_url linking directly to the note in the MantisBT web UI. Full UTF-8 text is supported. Markdown syntax is stored as-is — rendering depends on the Ma...
AI agents use add_note 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 |
|---|---|---|---|
text | string | Yes | Note text (minimum 1 character). Full UTF-8 including emoji is supported. Markdown is stored as-is. |
issue_id | integer | Yes | Numeric issue ID — use list_issues or get_issue to obtain issue IDs |
view_state | string | — | Visibility of the note: "public" (visible to all, default) or "private" (visible only to users with sufficient access level). |
Parameters from the server's own tool schema.
add_note creates new note/comment records in MantisBT issues, which is a reversible Write operation. The blast radius is minimal: notes can be edited or deleted later, no permanent data destruction occurs, no financial impact, and the operation is confined to issue comments. The ability to mark notes as private (view_state="private") is a standard access control feature, not a severity escalator.
From the tool's definition Tool description states it 'Add a note (comment) to an existing MantisBT issue' and 'Returns the created note object' — this is a create operation that adds new data to an issue.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Add a note (comment) to an existing MantisBT issue. Returns the created note object including id, created_at, reporter, text, view_state, and a view_url linking directly to the note in the MantisBT web UI. Full UTF-8 text is supported. Markdown syntax is stored as-is — rendering depends on the MantisBT instance's configured text renderer. Use view_state="private" to restrict the note to users with reporter-level access or higher; public notes are visible to all users who can view the issue. Prerequisites: obtain issue_id from list_issues, get_issue, or search_issues. 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.
add_note accepts 3 parameters: text, issue_id, view_state. Required: text, issue_id. 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 add_note: 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.
add_note 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 add_note 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 add_note. 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.
add_note 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 →