获取当前工作区所有文件的诊断信息（错误/警告/提示）。返回完整的诊断列表，包含所有文件的详细错误信息。
AI agents call getDiagnostics 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 performs a simple query/fetch operation across workspace diagnostics. It has no side effects: it does not create, modify, delete, or execute anything. The data returned is diagnostic metadata (errors/warnings/hints) generated by the IDE itself, not arbitrary code execution or data manipulation. Misuse by an AI agent would be limited to information disclosure or noisy reports, hence 'low' severity.
From the tool's definition Tool description states it 'retrieves diagnostic information (errors/warnings/hints)' and 'returns complete diagnostic list' — purely read operations with no modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access getDiagnostics 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 getDiagnostics:
{
"version": "1",
"default": "deny",
"tools": {
"getDiagnostics": {}
}
}getDiagnostics 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 getDiagnostics: 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.
getDiagnostics 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 getDiagnostics 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 getDiagnostics. 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.
getDiagnostics 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.