detach_tag · MantisBT MCP Server MCP: Risk & Policy

WHAT IT DOES

What detach_tag does on MantisBT MCP Server

AI agents use detach_tag 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
`tag_id`	integer	Yes	Numeric tag ID to remove
`issue_id`	integer	Yes	Numeric issue ID

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why detach_tag needs a policy

Detaching a tag modifies the issue's metadata by removing an association, but it is reversible (the tag can be re-attached). It does not delete the tag itself or the issue, so it falls under Write rather than Destructive. Misuse could disrupt issue categorization and searchability, giving it medium severity.

From the tool's definition Remove a tag from a MantisBT issue

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

detach_tag Rate-limited

detach_tag 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": {
    "detach_tag": {
      "limits": [
        {
          "counter": "detach_tag_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 detach_tag

What does the detach_tag tool do? +

Remove a tag from a MantisBT issue. Requires tag_detach_own_threshold (default: REPORTER) for own tags, or tag_detach_threshold (default: DEVELOPER) for tags attached by others. 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 detach_tag accept? +

detach_tag accepts 2 parameters: tag_id, issue_id. Required: tag_id, issue_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on detach_tag? +

Register the MantisBT MCP Server MCP server in PolicyLayer and add a rule for detach_tag: 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 detach_tag? +

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

Can I rate-limit detach_tag? +

Yes. Add a rate_limit block to the detach_tag 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 detach_tag completely? +

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

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