Create a new MantisBT issue. Returns the full created issue object including the assigned id, summary, status, priority, severity, category, reporter, created_at, and view_url. Required fields: summary, description, project_id, category. All other fields are optional with sensible defaults (prior...
AI agents use create_issue 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 |
|---|---|---|---|
handler | string | — | MantisBT login name of the assignee. The server resolves the name to a user ID from the project member list. Use find_project_member or get_project_users to loo |
summary | string | Yes | Issue summary/title (required) |
version | string | — | Affected product version name. Use get_project_versions to list available version names for the project. |
category | string | Yes | Category name (required). Use get_project_categories to list available categories for the project. |
priority | string | — | Priority level. Canonical English names: none, low, normal, high, urgent, immediate. Default: "normal". Use get_issue_enums to see localized labels. |
severity | string | — | Severity level. Canonical English names: feature, trivial, text, tweak, minor, major, crash, block. Default: "minor". Use get_issue_enums to see localized label |
handler_id | integer | — | Numeric user ID of the assignee. Alternative to the handler field — use one or the other, not both. |
project_id | integer | Yes | Project ID the issue belongs to — use list_projects to discover project IDs |
view_state | string | — | Visibility of the issue: "public" (visible to all, default) or "private" (restricted to higher-access users). |
description | string | Yes | Detailed issue description (required). Do not create issues without a description. Plain text or Markdown. |
custom_fields | array | — | Custom field values: [{field: {id|name}, value: "<string>"}]. Use get_issue_fields or get_metadata to discover available custom fields per project. |
target_version | string | — | Target fix version — version in which the issue is planned to be resolved. Use get_project_versions to list available version names. |
Parameters from the server's own tool schema.
This tool creates new records in a bug tracking system, which is a reversible write operation. While it modifies system state by adding data, the action is not destructive (issues can be deleted via delete_issue) and does not involve financial transactions.
From the tool's definition Tool description states 'Create a new MantisBT issue' and 'Returns the full created issue object including the assigned id'. The tool creates new data (issues) in the system with persistent identifiers, modifying the state of the MantisBT instance.
Risk signalsHigh parameter count (20 properties)
Attacks that exploit this kind of access
Create a new MantisBT issue. Returns the full created issue object including the assigned id, summary, status, priority, severity, category, reporter, created_at, and view_url. Required fields: summary, description, project_id, category. All other fields are optional with sensible defaults (priority: "normal", severity: "minor"). Recommended workflow: 1. Call get_project_categories to obtain a valid category name 2. Optionally call get_project_versions to obtain version names 3. Optionally call find_project_member to resolve the assignee's username Both priority and severity accept canonical English names or localized labels from the connected MantisBT instance — call get_issue_enums to see all available values. For the handler, prefer the username field (resolved server-side) over handler_id when working interactively. 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.
create_issue accepts 12 parameters: handler, summary, version, category, priority, severity, handler_id, project_id, view_state, description, custom_fields, target_version. Required: summary, category, project_id, description. 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 create_issue: 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.
create_issue 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 create_issue 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 create_issue. 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.
create_issue 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 →