// MCP TOOL REFERENCE

MCP DIAGNOSTICS EXTENSION TOOLS

5 tools from the MCP Diagnostics Extension MCP Server, categorised by risk level.

View the MCP Diagnostics Extension policy →
// ALL 5 MCP DIAGNOSTICS EXTENSION TOOLS
READ 5 tools
Read getPerformanceMetrics Get performance metrics and health information Read getProblems Get all current problems/diagnostics from VS Code workspace analysis Read getProblemsForFile Get problems for a specific file Read getProblemsForWorkspace Get problems for specific workspace Read getWorkspaceSummary Get summary statistics of problems across workspace

Route MCP Diagnostics Extension through PolicyLayer and every one of its 5 tools is checked against your policy before it runs.

CHECK YOUR STACK →

See every tool, the dangerous ones, and the token cost across your stack.

// FAQ
How many tools does the MCP Diagnostics Extension MCP server have? +

The MCP Diagnostics Extension MCP server exposes 5 tools across 1 categories: Read.

How do I enforce policies on MCP Diagnostics Extension tools? +

Route the MCP Diagnostics Extension server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do MCP Diagnostics Extension tools fall into? +

MCP Diagnostics Extension tools are categorised as Read (5). Each category has a recommended default policy.

Enforce policy on every MCP Diagnostics Extension tool call.

Start from MCP Diagnostics Extension, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.