List all tags defined in the MantisBT installation. The MantisBT REST API exposes a GET /tags endpoint on some installations. If that endpoint is not available, this tool falls back to the local metadata cache populated by sync_metadata.
AI agents call list_tags 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) |
page_size | integer | — | Tags per page (default: 50) |
Parameters from the server's own tool schema.
This tool retrieves and queries tag metadata with no side effects. It is purely informational—it neither creates, modifies, deletes, nor executes anything. The fallback to a local cache does not change its read-only nature. Severity is low because tag enumeration poses minimal risk even if exposed to an untrusted agent.
From the tool's definition Tool description states 'List all tags defined in the MantisBT installation' using GET /tags endpoint or metadata cache lookup. No modification, deletion, or execution occurs.
Attacks that exploit this kind of access
List all tags defined in the MantisBT installation. The MantisBT REST API exposes a GET /tags endpoint on some installations. If that endpoint is not available, this tool falls back to the local metadata cache populated by sync_metadata. It is categorised as a Read tool in the MantisBT MCP Server MCP Server, which means it retrieves data without modifying state.
list_tags accepts 2 parameters: page, page_size. 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_tags: 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_tags 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_tags 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_tags. 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_tags 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 →