Remove a relationship from a MantisBT issue. Use get_issue first to retrieve the relationship IDs. The relationship_id is the numeric id field of a relationship object in the issue's relationships array (not the type ID).
AI agents call remove_relationship to permanently remove resources in MantisBT MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
issue_id | integer | Yes | The issue ID the relationship belongs to |
relationship_id | integer | Yes | The numeric ID of the relationship to remove (from the relationships array in get_issue) |
Parameters from the server's own tool schema.
Removing a relationship is an irreversible deletion of a linkage between issues. There is no indication of an undo mechanism, and the description explicitly states 'remove', making this a destructive operation. Severity is medium because only a relationship link is deleted, not the issues themselves.
From the tool's definition Remove a relationship from a MantisBT issue
Attacks that exploit this kind of access
Remove a relationship from a MantisBT issue. Use get_issue first to retrieve the relationship IDs. The relationship_id is the numeric id field of a relationship object in the issue's relationships array (not the type ID). It is categorised as a Destructive tool in the MantisBT MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_relationship accepts 2 parameters: issue_id, relationship_id. Required: issue_id, relationship_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 remove_relationship: 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.
remove_relationship is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_relationship 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 remove_relationship. 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.
remove_relationship 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 →