remove_monitor · MantisBT MCP Server MCP: Risk & Policy

WHAT IT DOES

What remove_monitor does on MantisBT MCP Server

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

PARAMETERS

Parameter	Type	Required	Description
`issue_id`	integer	Yes	Numeric issue ID
`username`	string	Yes	Username of the monitor to remove

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why remove_monitor needs a policy

This tool modifies a monitoring/subscription list by removing a user, which is a reversible write operation (the user can be re-added via add_monitor). It does not delete data, execute code, or have financial implications. The blast radius is low as it only affects notification delivery for one user on one issue.

From the tool's definition Remove a user from the monitor list of a MantisBT issue. The user will no longer receive email notifications for updates to this issue.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_monitor Rate-limited

remove_monitor 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": {
    "remove_monitor": {
      "limits": [
        {
          "counter": "remove_monitor_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MantisBT MCP Server, so you can run agents against it safely.

FAQ

Questions about remove_monitor

What does the remove_monitor tool do? +

Remove a user from the monitor list of a MantisBT issue. The user will no longer receive email notifications for updates to this issue. 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.

What parameters does remove_monitor accept? +

remove_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.

How do I enforce a policy on remove_monitor? +

Register the MantisBT MCP Server MCP server in PolicyLayer and add a rule for remove_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.

What risk level is remove_monitor? +

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

Can I rate-limit remove_monitor? +

Yes. Add a rate_limit block to the remove_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.

How do I block remove_monitor completely? +

Set action: deny in the PolicyLayer policy for remove_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.

What MCP server provides remove_monitor? +

remove_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.