AI agents call getDiagnosticsForFile 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 diagnostic information (errors/warnings/hints) from the IDE for a specific file. It performs a data query operation without modifying, deleting, or executing anything. The function is purely informational and read-only, making it a Read category tool. The low severity reflects minimal risk even if misused by an AI agent, as it only exposes diagnostic metadata about code.
From the tool's definition Tool name 'getDiagnosticsForFile' and description '获取指定文件的诊断信息' (get diagnostic information for specified file) indicate retrieval of diagnostic data.
Documented attack patterns abuse exactly the kind of access getDiagnosticsForFile 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 getDiagnosticsForFile:
{
"version": "1",
"default": "deny",
"tools": {
"getDiagnosticsForFile": {}
}
}getDiagnosticsForFile 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.
获取指定文件的诊断信息。⚠️ 注意：需要使用完整的workspace URI格式，如. 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 getDiagnosticsForFile: 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.
getDiagnosticsForFile 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 getDiagnosticsForFile 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 getDiagnosticsForFile. 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.
getDiagnosticsForFile 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.