List all versions defined for a MantisBT project. Returns an array of version objects, each containing id, name, released (boolean), obsolete (boolean), and optionally a date field. Use the returned version names directly when creating or updating issues via create_issue and update_issue (version...
AI agents call get_project_versions 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 |
|---|---|---|---|
inherit | boolean | — | Include versions inherited from parent projects. Default: false. Set to true for sub-projects that share versions with a parent project. |
obsolete | boolean | — | Include obsolete (deprecated) versions in the response. Default: false. Set to true to see all versions including those no longer actively used. |
project_id | integer | Yes | Numeric project ID — use list_projects to discover project IDs |
Parameters from the server's own tool schema.
This tool retrieves and queries existing version data from a MantisBT project without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval function with no side effects, making it a Read category tool with low severity risk.
From the tool's definition Tool description states it "List all versions defined for a MantisBT project" and "Returns an array of version objects". The description explicitly indicates this is a retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
List all versions defined for a MantisBT project. Returns an array of version objects, each containing id, name, released (boolean), obsolete (boolean), and optionally a date field. Use the returned version names directly when creating or updating issues via create_issue and update_issue (version, target_version, fixed_in_version fields). By default, obsolete and inherited parent-project versions are excluded. Set obsolete=true to include deprecated versions; set inherit=true to also return versions from parent projects. Prerequisites: obtain project_id from list_projects. It is categorised as a Read tool in the MantisBT MCP Server MCP Server, which means it retrieves data without modifying state.
get_project_versions accepts 3 parameters: inherit, obsolete, project_id. Required: project_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 get_project_versions: 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.
get_project_versions 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 get_project_versions 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 get_project_versions. 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.
get_project_versions 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 →