Projects — list all qTest projects, or fetch a single project by ID
AI agents call list-projects to retrieve information from qTest 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 and queries project information from qTest Manager without any side effects. It performs a read-only operation consistent with the 'Read' category, which encompasses search, list, get, and fetch operations. The severity is low because exposure of this tool to an AI agent would only allow viewing existing project data, with minimal blast radius.
From the tool's definition Tool name 'list-projects' and description 'list all qTest projects, or fetch a single project by ID' indicate data retrieval operations with no modification, creation, or deletion of resources.
Attacks that exploit this kind of access
Projects — list all qTest projects, or fetch a single project by ID. It is categorised as a Read tool in the qTest MCP Server MCP Server, which means it retrieves data without modifying state.
Register the qTest 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 qTest 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 qTest MCP Server MCP server (usman-ghani123/qtest-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 →