Low Risk

get_diagnostics_code

CRITICAL: Run this after EVERY series of code changes to check for errors before completing tasks. Analyzes code for warnings and errors using VS Code

How to control get_diagnostics_code ↓

What get_diagnostics_code does on Vscode

AI agents call get_diagnostics_code to retrieve information from Vscode without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_diagnostics_code needs a policy

This tool retrieves diagnostic information (errors, warnings) from VS Code's analysis of code. It has no side effects—it does not modify files, execute commands, delete data, or trigger external operations. Despite the 'CRITICAL' framing in the description (which appears to be instructional emphasis rather than functional severity), the tool itself is purely informational and read-only.

From the tool's definition Tool analyzes code for warnings and errors, examining diagnostic information from VS Code. The description explicitly states it 'Analyzes code for warnings and errors' which is a read-only operation that retrieves diagnostic data without modifying files or…

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access get_diagnostics_code gives an agent:

How to control get_diagnostics_code

PolicyLayer is an MCP gateway — it sits between your AI agents and Vscode, and nothing reaches the server without passing your rules. This is the rule we recommend for get_diagnostics_code:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_diagnostics_code": {}
  }
}

get_diagnostics_code is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Vscode — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_diagnostics_code

What does the get_diagnostics_code tool do? +

CRITICAL: Run this after EVERY series of code changes to check for errors before completing tasks. Analyzes code for warnings and errors using VS Code. It is categorised as a Read tool in the Vscode MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_diagnostics_code? +

Register the Vscode MCP server in PolicyLayer and add a rule for get_diagnostics_code: 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 Vscode. Nothing to install.

What risk level is get_diagnostics_code? +

get_diagnostics_code is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_diagnostics_code? +

Yes. Add a rate_limit block to the get_diagnostics_code 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.

How do I block get_diagnostics_code completely? +

Set action: deny in the PolicyLayer policy for get_diagnostics_code. 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.

What MCP server provides get_diagnostics_code? +

get_diagnostics_code is provided by the Vscode MCP server (juehang/vscode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Vscode tool call.

Start from Vscode, 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.

12 Vscode tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.