获取项目级代码规约扫描摘要，包含各工具（P3C/ESLint/Stylelint/Checkstyle）的违规总数。
AI agents call get_project_summary to retrieve information from YanceLint 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 aggregated summary statistics from linting analysis already performed by external tools. It reads and returns violation metrics without triggering linting runs, modifying code, deleting anything, or executing arbitrary operations. The action is informational and read-only, falling clearly into the Read category.
From the tool's definition Tool description states it 'gets' (获取) 'project-level code convention scan summary' (项目级代码规约扫描摘要) containing violation counts from various linting tools.
Attacks that exploit this kind of access
获取项目级代码规约扫描摘要，包含各工具（P3C/ESLint/Stylelint/Checkstyle）的违规总数。. It is categorised as a Read tool in the YanceLint MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YanceLint MCP Server MCP server in PolicyLayer and add a rule for get_project_summary: 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 YanceLint MCP Server. Nothing to install.
get_project_summary 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 get_project_summary 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 get_project_summary. 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.
get_project_summary is provided by the YanceLint MCP Server MCP server (xihe-lab/yance-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 →