Add a relationship between two MantisBT issues. Relationship types — use either type_id (numeric) or type_name (string): - 0 / "duplicate_of" — this issue is a duplicate of target - 1 / "related_to" — this issue is related to target - 2 / "parent_of" — this issue depends on target (target must be...
AI agents use add_relationship 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 |
|---|---|---|---|
type_id | integer | — | Relationship type ID: 0=duplicate_of, 1=related_to, 2=parent_of (depends on), 3=child_of (blocks), 4=has_duplicate. Use either type_id or type_name. |
issue_id | integer | Yes | The source issue ID (the one the relationship is added to) |
target_id | integer | Yes | The target issue ID |
type_name | string | — | Relationship type name as alternative to type_id. Accepted: "duplicate_of", "related_to", "parent_of" (or "depends_on"), "child_of" (or "blocks"), "has_duplicat |
Parameters from the server's own tool schema.
This tool creates or modifies relationships between issues, which is a reversible change to issue metadata. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool description states 'Add a relationship between two MantisBT issues' with relationship types like 'duplicate_of', 'related_to', 'parent_of', 'child_of', 'has_duplicate'.
Attacks that exploit this kind of access
Add a relationship between two MantisBT issues. Relationship types — use either type_id (numeric) or type_name (string): - 0 / "duplicate_of" — this issue is a duplicate of target - 1 / "related_to" — this issue is related to target - 2 / "parent_of" — this issue depends on target (target must be done first); alias: "depends_on" - 3 / "child_of" — this issue blocks target (target can't proceed until this is done); alias: "blocks" - 4 / "has_duplicate" — this issue has target as a duplicate Directionality note: "A child_of B" means A blocks B. "A parent_of B" means A depends on B. Dash variants (e.g. "related-to") are also accepted for type_name. 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_relationship accepts 4 parameters: type_id, issue_id, target_id, type_name. Required: issue_id, target_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 add_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.
add_relationship 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_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 add_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.
add_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 →