Manage code folding: create, open, close, and toggle folds
AI agents use vim_fold to create or update resources in Mcp Neovim Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Neovim Server environment.
Folding operations create and modify fold markers/state within a buffer, which is a reversible write action. While folding doesn't permanently delete data, it does alter editor state. This is less severe than Execute (which would run code) but qualifies as Write rather than Read because it modifies buffer state.
From the tool's definition Tool manages code folding with 'create, open, close, and toggle folds' operations - these are reversible state modifications to the editor's folding state without deleting or executing code.
Attacks that exploit this kind of access
Manage code folding: create, open, close, and toggle folds. It is categorised as a Write tool in the Mcp Neovim Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Neovim Server MCP server in PolicyLayer and add a rule for vim_fold: 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_fold is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vim_fold 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_fold. 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_fold 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 →