// SCAN REPORT

MantisBT MCP Server

34 tools. 12 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated: 5 Jul 2026

12 can modify or destroy data

22 read-only

34 tools total

Verified server · catalogue entry verified 05/07/2026 · full schemas captured for 25 of 34 tools

How to control MantisBT MCP Server ↓

TOOL MAP

What MantisBT MCP Server exposes to your agents

Read (22) Write / Execute (9) Destructive / Financial (3)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What MantisBT MCP Server costs in tokens

8,124 tokens of tool definitions, loaded on every request

4.1% of a 200k context window

881 heaviest tool: create_issue

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous MantisBT MCP Server tools

Destructive · High delete_issue This tool irreversibly removes data (an entire issue record) from the system. Destructive · High delete_note This tool irreversibly deletes data (notes) from a MantisBT issue and cannot be undone. Destructive · Medium remove_relationship Removing a relationship is an irreversible deletion of a linkage between issues. Write · Medium detach_tag Detaching a tag modifies the issue's metadata by removing an association, but it is reversible (the tag can be re-attached).

12 of MantisBT MCP Server's 34 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control MantisBT MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and MantisBT MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_issue": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_monitor": {
    "limits": [
      {
        "counter": "add_monitor_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "find_project_member": {
    "limits": [
      {
        "counter": "find_project_member_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register MantisBT MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MANTISBT →

Instant setup, no code required.

FULL CATALOGUE

All 34 MantisBT MCP Server tools

DESTRUCTIVE 3 tools

Destructive delete_issue Permanently delete a MantisBT issue. This action is irreversible. Destructive delete_note Permanently delete a note from a MantisBT issue. This action is irreversible — deleted notes cannot be recover Destructive remove_relationship Remove a relationship from a MantisBT issue. Use get_issue first to retrieve the relationship IDs. The relati

WRITE 9 tools

Write add_monitor Add a user as a monitor (watcher) of a MantisBT issue. Monitors receive email notifications whenever the issue Write add_note Add a note (comment) to an existing MantisBT issue. Returns the created note object including id, created_at, Write add_relationship Add a relationship between two MantisBT issues. Relationship types — use either type_id (numeric) or type_nam Write attach_tags Attach one or more tags to a MantisBT issue. Each tag can be specified either by ID or by name. If a tag name Write create_issue Create a new MantisBT issue. Returns the full created issue object including the assigned id, summary, status, Write detach_tag Remove a tag from a MantisBT issue. Requires tag_detach_own_threshold (default: REPORTER) for own tags, or ta Write remove_monitor Remove a user from the monitor list of a MantisBT issue. The user will no longer receive email notifications f Write update_issue Update one or more fields of an existing MantisBT issue using a partial PATCH. The "fields" object accepts an Write upload_file Upload a file as an attachment to a MantisBT issue. Adds the file to the issue without modifying any issue fie

READ 22 tools

Read find_project_member Search for users with access to a MantisBT project by name, display name, or email. Returns up to limit match Read get_config Retrieve one or more MantisBT configuration options. Common option names: - "status_enum_string" — issue stat Read get_current_user Retrieve the profile of the user associated with the current API key. Read get_issue Retrieve a single MantisBT issue by its numeric ID. Returns all issue fields including notes, attachments, and Read get_issue_enums Return valid ID, name, and (if available) localized label for all issue enum fields. Use this tool before cre Read get_issue_fields Return all field names that are valid for the "select" parameter of list_issues and get_issue. Fields are dis Read get_issues Retrieve multiple MantisBT issues by their numeric IDs in a single MCP call. Requests run in parallel (max 5 c Read get_mantis_version Returns the version of the connected MantisBT installation and optionally compares it against the latest offic Read get_mcp_version Returns the version of this mantisbt-mcp-server instance. Read get_metadata Return a compact summary of cached MantisBT metadata: project count, tag count, and per-project counts of user Read get_metadata_full Return the complete raw MantisBT metadata cache: all projects with full fields, and per-project lists of users Read get_project_categories List all categories available for a MantisBT project. Note: The MantisBT API returns global (cross-project) c Read get_project_users List all users with access to a specific MantisBT project. Returns an array of user objects, each containing i Read get_project_versions List all versions defined for a MantisBT project. Returns an array of version objects, each containing id, nam Read list_filters List all saved MantisBT issue filters accessible to the current user. Filter IDs can be used with list_issues. Read list_issue_files List all file attachments of a MantisBT issue. Returns an array of attachment objects, each containing id, fil Read list_issues List MantisBT issues with optional filtering. Returns a paginated list of issues. Use the "select" parameter t Read list_languages List all languages supported by the MantisBT installation. Read list_notes List all notes (comments) attached to a MantisBT issue. Note: get_issue already includes notes in its response Read list_projects List all MantisBT projects accessible to the current API user. Read sync_metadata Fetch all projects and their associated users, versions, categories, and tags from MantisBT and store them in

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about MantisBT MCP Server

Can an AI agent delete data through the MantisBT MCP Server MCP server? +

Yes. The MantisBT MCP Server server exposes 3 destructive tools including delete_issue, delete_note, remove_relationship. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through MantisBT MCP Server? +

The MantisBT MCP Server server has 9 write tools including add_monitor, add_note, add_relationship. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach MantisBT MCP Server.

How many tools does the MantisBT MCP Server MCP server expose? +

34 tools across 3 categories: Destructive, Read, Write. 22 are read-only. 12 can modify, create, or delete data.

How do I enforce a policy on MantisBT MCP Server? +

Register the MantisBT MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every MantisBT MCP Server tool call.

Deterministic rules across all 34 MantisBT MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MANTISBT →

Instant setup, no code required.

34 MantisBT MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.