Check Neovim connection health
AI agents call vim_health to retrieve information from Mcp Neovim Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A health check tool reads and reports the status of a connection without modifying any state. It is purely informational with no side effects, making it a Read category tool with low severity.
From the tool's definition "Check Neovim connection health" - this is a diagnostic/status check operation
Attacks that exploit this kind of access
Check Neovim connection health. It is categorised as a Read tool in the Mcp Neovim Server MCP Server, which means it retrieves data without modifying state.
Register the Mcp Neovim Server MCP server in PolicyLayer and add a rule for vim_health: 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 Neovim Server. Nothing to install.
vim_health 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 vim_health 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 vim_health. 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.
vim_health is provided by the Mcp Neovim Server MCP server (mcp-neovim-server). 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 →