List all users with access to a specific MantisBT project. Returns an array of user objects, each containing id, name (login name), real_name, email, and access_level fields. Use get_project_users when you need the complete user list for a project — for example, to verify who has access or to bui...
AI agents call get_project_users 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 |
|---|---|---|---|
project_id | integer | Yes | Numeric project ID — use list_projects to discover project IDs |
access_level | integer | — | Return only users at or above this access level. Common values: 10=viewer, 25=reporter, 40=updater, 55=developer, 70=manager, 90=administrator. Omit to return a |
Parameters from the server's own tool schema.
This tool retrieves and queries user data from a project without modifying, executing, deleting, or creating any resources. It has no side effects beyond returning existing information. The blast radius of misuse is low—an adversary could enumerate users and their access levels, which is an information disclosure risk but does not compromise data integrity or enable further damaging actions without additional tools.
From the tool's definition Tool name 'get_project_users' and description explicitly states 'List all users with access to a specific MantisBT project. Returns an array of user objects.' The verb 'list' and 'returns' indicate data retrieval with no side effects.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
List all users with access to a specific MantisBT project. Returns an array of user objects, each containing id, name (login name), real_name, email, and access_level fields. Use get_project_users when you need the complete user list for a project — for example, to verify who has access or to build a handler list. For name-based lookup of a single user, prefer find_project_member which supports case-insensitive substring search and is significantly faster on large projects. Access level IDs: 10=viewer, 25=reporter, 40=updater, 55=developer, 70=manager, 90=administrator. 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_users accepts 2 parameters: project_id, access_level. 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_users: 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_users 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_users 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_users. 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_users 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 →