List MantisBT issues with optional filtering. Returns a paginated list of issues. Use the "select" parameter to limit returned fields and reduce response size significantly. Note: "assigned_to", "reporter_id", "status", and date filters are applied client-side (the MantisBT REST API does not supp...
AI agents call list_issues to retrieve information from MantisBT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | — | Page number (default: 1) |
sort | string | — | Sort field (e.g. "last_updated", "id") |
select | string | — | Comma-separated list of fields to include in the response (server-side projection). Significantly reduces response size. Example: "id,summary,status,priority,ha |
status | string | — | Filter issues by status name (e.g. "new", "feedback", "acknowledged", "confirmed", "assigned", "resolved", "closed") or use "open" as shorthand for all statuses |
direction | string | — | Sort direction |
filter_id | integer | — | Use a saved MantisBT filter ID |
page_size | integer | — | Issues per page (default: 50, max: 50) |
project_id | integer | — | Filter by project ID |
assigned_to | integer | — | Filter by handler/assignee user ID |
reporter_id | integer | — | Filter by reporter user ID |
created_after | string | — | ISO-8601 timestamp — only return issues created after this date (exclusive). Example: "2026-03-01T00:00:00Z" |
updated_after | string | — | ISO-8601 timestamp — only return issues updated after this date (exclusive). Example: "2026-03-25T00:00:00Z" |
Parameters from the server's own tool schema.
This tool performs read-only operations on issue data. It retrieves and filters existing issues without creating, modifying, deleting, or executing any operations. The client-side filtering and pagination are mechanisms for data retrieval, not mutation.
From the tool's definition Tool description states it "List MantisBT issues" and "Returns a paginated list of issues" with filtering capabilities.
Risk signalsHigh parameter count (14 properties)
Attacks that exploit this kind of access
List MantisBT issues with optional filtering. Returns a paginated list of issues. Use the "select" parameter to limit returned fields and reduce response size significantly. Note: "assigned_to", "reporter_id", "status", and date filters are applied client-side (the MantisBT REST API does not support these as server-side filters). When any of these filters are active the tool automatically fetches multiple pages internally until enough matching results are found (up to 500 issues scanned). The "page" and "page_size" parameters refer to the resulting filtered list. Tip for date queries: fetching with select="id,updated_at,created_at" plus a date filter is very compact and efficient. It is categorised as a Read tool in the MantisBT MCP Server MCP Server, which means it retrieves data without modifying state.
list_issues accepts 12 parameters: page, sort, select, status, direction, filter_id, page_size, project_id, assigned_to, reporter_id, created_after, updated_after. 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 list_issues: 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.
list_issues is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_issues 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 list_issues. 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.
list_issues 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 →