AI agents call get_state 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.
This tool retrieves or inspects the state of a running Neovim session without modifying data or executing arbitrary code. While the server supports command execution capabilities, 'get_state' itself appears designed for querying state information only, making it a Read operation.
From the tool's definition Tool name 'get_state' combined with server description mentioning 'state inspection' indicates retrieval of state from Neovim; sibling tools include 'get_state_brief' and 'get_all_diagnostics' which are clearly Read operations.
Documented attack patterns abuse exactly the kind of access get_state 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 get_state:
{
"version": "1",
"default": "deny",
"tools": {
"get_state": {}
}
}get_state is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_state. It is categorised as a Read tool in the Nvim MCP Server, which means it retrieves data without modifying state.
Register the Nvim MCP server in PolicyLayer and add a rule for get_state: 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.
get_state 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 get_state 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 get_state. 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.
get_state 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.
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.