Get only info-level diagnostics from the workspace
AI agents call get_info 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 diagnostic information at the info severity level from the VS Code workspace. It has no side effects, does not execute code, does not modify data, and does not delete or move resources. It is purely a query tool that returns existing diagnostic data. The low severity reflects minimal blast radius—returning diagnostic messages cannot harm systems or data.
From the tool's definition Tool name 'get_info' and description 'Get only info-level diagnostics from the workspace' indicate a retrieval operation. The description explicitly uses 'Get', which is a read-only operation.
Attacks that exploit this kind of access
Get only info-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_info: 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_info 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_info 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_info. 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_info 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 →