List all MantisBT projects accessible to the current API user.
AI agents call list_projects 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.
This tool retrieves project information from MantisBT without causing any side effects, state changes, or irreversible actions. It is a simple query/list operation that fits the Read category. Severity is low because the data returned is typically project metadata that authorized users should be able to access, with minimal risk of misuse.
From the tool's definition Tool name 'list_projects' and description 'List all MantisBT projects accessible to the current API user' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
List all MantisBT projects accessible to the current API user. It is categorised as a Read tool in the MantisBT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MantisBT MCP Server MCP server in PolicyLayer and add a rule for list_projects: 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_projects 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_projects 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_projects. 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_projects 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 →