Get summary statistics of problems across workspace
AI agents call getWorkspaceSummary to retrieve information from MCP Diagnostics Extension without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries workspace diagnostics to provide summary statistics. It has no side effects, does not execute code, does not modify data, and does not create financial obligations. It is purely informational, consistent with other Read category tools like 'getProblems' and 'getProblemsForWorkspace' on the same server that expose VS Code diagnostics in real-time to AI agents.
From the tool's definition Tool name 'getWorkspaceSummary' and description 'Get summary statistics of problems across workspace' indicate a read-only operation that retrieves and aggregates diagnostic data without modifying any state.
Documented attack patterns abuse exactly the kind of access getWorkspaceSummary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Diagnostics Extension, and nothing reaches the server without passing your rules. This is the rule we recommend for getWorkspaceSummary:
{
"version": "1",
"default": "deny",
"tools": {
"getWorkspaceSummary": {}
}
} getWorkspaceSummary 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.
Get summary statistics of problems across workspace. It is categorised as a Read tool in the MCP Diagnostics Extension MCP Server, which means it retrieves data without modifying state.
Register the MCP Diagnostics Extension MCP server in PolicyLayer and add a rule for getWorkspaceSummary: 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 Extension. Nothing to install.
getWorkspaceSummary 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 getWorkspaceSummary 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 getWorkspaceSummary. 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.
getWorkspaceSummary is provided by the MCP Diagnostics Extension MCP server (newbpydev/mcp-diagnostics-extension). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
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.
Free to start. No card required.
5 MCP Diagnostics Extension tools catalogued and risk-classified — across an index of 43,000+ MCP servers.