Low Risk

highlight_range

highlight_range

How to control highlight_range ↓

AI agents call highlight_range to retrieve information from Nvim without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Even though highlight_range only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Documented attack patterns abuse exactly the kind of access highlight_range gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Nvim, and nothing reaches the server without passing your rules. This is the rule we recommend for highlight_range:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "highlight_range": {}
  }
}

highlight_range is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Nvim — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the highlight_range tool do? +

highlight_range. It is categorised as a Read tool in the Nvim MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on highlight_range? +

Register the Nvim MCP server in PolicyLayer and add a rule for highlight_range: 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 Nvim. Nothing to install.

What risk level is highlight_range? +

highlight_range is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit highlight_range? +

Yes. Add a rate_limit block to the highlight_range 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.

How do I block highlight_range completely? +

Set action: deny in the PolicyLayer policy for highlight_range. 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.

What MCP server provides highlight_range? +

highlight_range is provided by the Nvim MCP server (paulburgess1357/nvim-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Nvim tool call.

Deterministic rules across all 17 Nvim tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

17 Nvim tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.