🌟 推荐工具：根据文件路径获取诊断信息，支持灵活的路径匹配。可以使用相对路径、文件名等多种格式，比 getDiagnosticsForFile 更易用。
AI agents call getDiagnosticsForPath 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 data (errors/warnings/hints) from the IDE based on a file path parameter. It has no side effects — it only queries and returns information. The slightly more flexible path matching compared to a sibling does not change its fundamental nature as a read operation.
From the tool's definition Tool name 'getDiagnosticsForFile' (sibling) and 'getDiagnosticsForPath' indicate retrieval operations. Description states '根据文件路径获取诊断信息' (get diagnostic information based on file path) — a read-only query operation.
Documented attack patterns abuse exactly the kind of access getDiagnosticsForPath 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 getDiagnosticsForPath:
{
"version": "1",
"default": "deny",
"tools": {
"getDiagnosticsForPath": {}
}
}getDiagnosticsForPath 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.
🌟 推荐工具：根据文件路径获取诊断信息，支持灵活的路径匹配。可以使用相对路径、文件名等多种格式，比 getDiagnosticsForFile 更易用。. 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 getDiagnosticsForPath: 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.
getDiagnosticsForPath 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 getDiagnosticsForPath 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 getDiagnosticsForPath. 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.
getDiagnosticsForPath 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.