获取诊断统计摘要，快速了解项目整体代码质量。返回文件总数、错误数量、警告数量的统计信息。
AI agents call getDiagnosticsSummary to retrieve information from MCP Diagnostics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves aggregated diagnostic statistics from the IDE. It performs no mutations, executions, financial operations, or destructive actions. It is purely informational, reading and summarizing existing diagnostic data. The low severity reflects that misuse (e.g., repeated calls) has negligible impact—it merely returns counts of code quality issues already detected by the IDE.
From the tool's definition Tool name 'getDiagnosticsSummary' and description indicate it 'returns statistical information' about diagnostic counts (files, errors, warnings). The verb 'get' and 'read' operation pattern confirm retrieval without modification.
Documented attack patterns abuse exactly the kind of access getDiagnosticsSummary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Diagnostics, and nothing reaches the server without passing your rules. This is the rule we recommend for getDiagnosticsSummary:
{
"version": "1",
"default": "deny",
"tools": {
"getDiagnosticsSummary": {}
}
}getDiagnosticsSummary 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.
获取诊断统计摘要，快速了解项目整体代码质量。返回文件总数、错误数量、警告数量的统计信息。. It is categorised as a Read tool in the MCP Diagnostics MCP Server, which means it retrieves data without modifying state.
Register the MCP Diagnostics MCP server in PolicyLayer and add a rule for getDiagnosticsSummary: 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 Diagnostics. Nothing to install.
getDiagnosticsSummary 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 getDiagnosticsSummary 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 getDiagnosticsSummary. 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.
getDiagnosticsSummary is provided by the MCP Diagnostics MCP server (lin037/mcp-diagnostics-trae). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Diagnostics, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 MCP Diagnostics tools catalogued and risk-classified — across an index of 43,000+ MCP servers.