AI agents call identify_project to retrieve information from MCP Code Indexer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns project identification information and status—a read-only operation with no side effects. It queries existing project data rather than creating, modifying, or executing any operations. The low severity reflects minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'identify_project' and description '识别代码项目，返回项目ID和状态' (identify code project, return project ID and status) indicate retrieval of project metadata. No modification, deletion, or command execution is described.
Documented attack patterns abuse exactly the kind of access identify_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Code Indexer, and nothing reaches the server without passing your rules. This is the rule we recommend for identify_project:
{
"version": "1",
"default": "deny",
"tools": {
"identify_project": {}
}
}identify_project is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
识别代码项目，返回项目ID和状态. It is categorised as a Read tool in the MCP Code Indexer MCP Server, which means it retrieves data without modifying state.
Register the MCP Code Indexer MCP server in PolicyLayer and add a rule for identify_project: 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 MCP Code Indexer. Nothing to install.
identify_project 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 identify_project 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 identify_project. 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.
identify_project is provided by the MCP Code Indexer MCP server (zxfgds/mcp-code-indexer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 MCP Code Indexer tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 MCP Code Indexer tools catalogued and risk-classified — across an index of 42,500+ MCP servers.