Replace one exact snippet in the current buffer or an optional file path. useLatestChangedTick is current-buffer-only; useLatestSessionChangedTick works for explicit path targets or already-open explicit bufferId targets in the editor session.
AI agents use replace_exact to create or update resources in Vigentic MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vigentic MCP environment.
This tool creates or modifies data reversibly by replacing text in files or buffers. It does not delete files or irreversibly destroy data (Destructive), nor does it execute arbitrary code or commands (Execute). The modification is targeted and reversible, making it a Write operation.
From the tool's definition "Replace one exact snippet in the current buffer or an optional file path" - the tool modifies file content by replacing text snippets, which is a reversible write operation.
Attacks that exploit this kind of access
Replace one exact snippet in the current buffer or an optional file path. useLatestChangedTick is current-buffer-only; useLatestSessionChangedTick works for explicit path targets or already-open explicit bufferId targets in the editor session. It is categorised as a Write tool in the Vigentic MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vigentic MCP server in PolicyLayer and add a rule for replace_exact: 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.
replace_exact 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 replace_exact 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 replace_exact. 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.
replace_exact 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 →