A warmed stdio MCP client measures connect cost plus repeated reads against the new resource surface, with comparable tool calls included as a baseline.
AI agents call get_diagnostics to retrieve information from Vigentic MCP 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 (likely code issues, errors, warnings from LSP) without modifying, deleting, or executing anything. It is a passive query operation returning analysis results. The low severity reflects that misuse only exposes existing diagnostic data about code, with no side effects or risk of data loss or code execution.
From the tool's definition Tool name 'get_diagnostics' and server description indicating 'LSP-powered diagnostics' suggest retrieval of code analysis data. The tool description mentions 'repeated reads against the new resource surface', indicating a read operation.
Attacks that exploit this kind of access
A warmed stdio MCP client measures connect cost plus repeated reads against the new resource surface, with comparable tool calls included as a baseline. It is categorised as a Read tool in the Vigentic MCP MCP Server, which means it retrieves data without modifying state.
Register the Vigentic MCP server in PolicyLayer and add a rule for get_diagnostics: 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 Vigentic MCP. Nothing to install.
get_diagnostics 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_diagnostics 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_diagnostics. 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_diagnostics is provided by the Vigentic MCP server (munozu/vigentic-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 →