List file-backed open buffers and whether they are dirty or current.
AI agents call list_open_buffers 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 only retrieves and reports the current state of open buffers in the Neovim IDE. It has no side effects, creates no new data, modifies no existing data, and executes no external code. It is a pure query/inspection operation, fitting the Read category with low severity since buffer listing poses minimal risk regardless of how an AI agent uses it.
From the tool's definition The tool 'list_open_buffers' returns status information about open buffers (dirty/current state) without modifying any data. The description explicitly states it 'List[s]' buffers, which is a read-only query operation.
Attacks that exploit this kind of access
List file-backed open buffers and whether they are dirty or current. 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 list_open_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 Vigentic MCP. Nothing to install.
list_open_buffers 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 list_open_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.
Set action: deny in the PolicyLayer policy for list_open_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.
list_open_buffers 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 →