Get only warning-level diagnostics from the workspace
AI agents call get_warnings to retrieve information from Diagnostics 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 and filters warning-level diagnostics from VS Code's diagnostic system. It is a read-only query operation with no side effects—it does not modify, execute, or delete anything. The operation has minimal blast radius even if an AI agent misuses it, as it only accesses diagnostic metadata that is already computed by the IDE. No code execution, data modification, or destructive actions are possible.
From the tool's definition Tool name 'get_warnings' and description 'Get only warning-level diagnostics from the workspace' indicate a retrieval operation that queries existing diagnostic data without modification, deletion, or execution.
Attacks that exploit this kind of access
Get only warning-level diagnostics from the workspace. It is categorised as a Read tool in the Diagnostics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Diagnostics MCP Server MCP server in PolicyLayer and add a rule for get_warnings: 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 Diagnostics MCP Server. Nothing to install.
get_warnings 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_warnings 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_warnings. 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_warnings is provided by the Diagnostics MCP Server MCP server (maaz0313-png/diagnostics-mcp). 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 →