Add a user as a monitor (watcher) of a MantisBT issue. Monitors receive email notifications whenever the issue is updated. Returns a success confirmation object. Use add_monitor to subscribe team members to issue updates without assigning them as the handler. To unsubscribe a user, call remove_mo...
AI agents use add_monitor 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 |
|---|---|---|---|
issue_id | integer | Yes | Numeric issue ID — use list_issues or get_issue to obtain issue IDs |
username | string | Yes | MantisBT login name (not the display name) of the user to add as monitor. Use find_project_member or get_project_users to discover valid login names for a proje |
Parameters from the server's own tool schema.
add_monitor creates or modifies data (adds a monitor relationship to an issue) without deleting or executing arbitrary code. This is a Write operation—it changes system state by establishing a new watcher subscription.
From the tool's definition Tool modifies issue state by adding a user as a monitor/watcher, creating a new subscription relationship. Description states 'Add a user as a monitor' and 'the operation succeeds' indicating a persistent state change.
Attacks that exploit this kind of access
Add a user as a monitor (watcher) of a MantisBT issue. Monitors receive email notifications whenever the issue is updated. Returns a success confirmation object. Use add_monitor to subscribe team members to issue updates without assigning them as the handler. To unsubscribe a user, call remove_monitor with the same parameters. Adding a user who is already a monitor is a no-op — the operation succeeds without creating duplicates. Prerequisites: obtain issue_id from list_issues or get_issue; use find_project_member or get_project_users to look up valid MantisBT login names. 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_monitor accepts 2 parameters: issue_id, username. Required: issue_id, username. 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_monitor: 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_monitor 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_monitor 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_monitor. 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_monitor 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 →