Low Risk

list_nvim_buffers

List all open buffers in Neovim instances running in the current directory

How to control list_nvim_buffers ↓

What list_nvim_buffers does on Neovim MCP Server

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

Low Risk

Why list_nvim_buffers needs a policy

This tool retrieves and lists information about open buffers in Neovim. It performs no data modification, deletion, code execution, or financial operations. The action is purely informational with no side effects, fitting the Read category. Severity is low because exposure of buffer names and metadata has minimal security impact—buffer contents are not returned, only a list of open files.

From the tool's definition Tool name 'list_nvim_buffers' and description 'List all open buffers in Neovim instances running in the current directory' indicate a read-only operation that retrieves buffer metadata without modification.

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

How to control list_nvim_buffers

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

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

list_nvim_buffers 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 Neovim MCP Server — 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.

Related tools and policies

Go deeper

Questions about list_nvim_buffers

What does the list_nvim_buffers tool do? +

List all open buffers in Neovim instances running in the current directory. It is categorised as a Read tool in the Neovim MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_nvim_buffers? +

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

What risk level is list_nvim_buffers? +

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

Can I rate-limit list_nvim_buffers? +

Yes. Add a rate_limit block to the list_nvim_buffers 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 list_nvim_buffers completely? +

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

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

Enforce policy on every Neovim MCP Server tool call.

Start from Neovim MCP Server, 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.

7 Neovim MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.