列出用户可访问的所有项目。返回项目标识和名称列表。
AI agents call list_projects to retrieve information from PingCode MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns project information without modifying, deleting, or executing operations. It is a straightforward read operation that retrieves project metadata. Low severity because exposure of project lists poses minimal risk compared to other categories—it may reveal organizational structure but cannot directly cause harm or data loss.
From the tool's definition Tool description translated: 'List all projects accessible to the user. Returns a list of project identifiers and names.' The verb 'list' and return-only behavior (project metadata) indicate data retrieval with no side effects.
Attacks that exploit this kind of access
列出用户可访问的所有项目。返回项目标识和名称列表。. It is categorised as a Read tool in the PingCode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PingCode 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 PingCode 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 PingCode MCP Server MCP server (ratatatat1/pingcode-mcp). 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 →