Search for users with access to a MantisBT project by name, display name, or email. Returns up to limit matching users (default: 10, max: 100). Matching is case-insensitive substring search across name, real_name, and email fields. Omit query to list the first limit users. Data is served from the...
AI agents call find_project_member 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 |
|---|---|---|---|
limit | integer | — | Maximum number of results to return (default: 10, max: 100) |
query | string | — | Case-insensitive substring to match against name, real_name, or email |
project_id | integer | Yes | Numeric project ID |
Parameters from the server's own tool schema.
This tool performs a search/query operation that retrieves user metadata without any side effects. It does not create, modify, delete, or execute any actions—it only returns matching user records. This is a classic Read operation with minimal security impact, hence low severity.
From the tool's definition Tool name is 'find_project_member' and description states it 'Search[es] for users with access to a MantisBT project' and 'Returns up to `limit` matching users'.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Search for users with access to a MantisBT project by name, display name, or email. Returns up to limit matching users (default: 10, max: 100). Matching is case-insensitive substring search across name, real_name, and email fields. Omit query to list the first limit users. Data is served from the local metadata cache when fresh; falls back to a live API call otherwise. It is categorised as a Read tool in the MantisBT MCP Server MCP Server, which means it retrieves data without modifying state.
find_project_member accepts 3 parameters: limit, query, 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 find_project_member: 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.
find_project_member 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 find_project_member 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 find_project_member. 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.
find_project_member 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 →