Approve and apply a previously validated edit from a dry run with edit_file_lines call using its stateId.
AI agents use approve_edit to create or update resources in Edit File Lines MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Edit File Lines MCP Server environment.
This tool creates or modifies file data (Write category). It does not delete or irreversibly overwrite content (not Destructive), nor does it execute arbitrary code or shell commands (not Execute).
From the tool's definition Tool description states 'Approve and apply a previously validated edit' — the action of applying an edit modifies file contents. The tool modifies text files based on a prior edit_file_lines call, which constitutes data modification.
Documented attack patterns abuse exactly the kind of access approve_edit gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Edit File Lines MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for approve_edit:
{
"version": "1",
"default": "deny",
"tools": {
"approve_edit": {
"limits": [
{
"counter": "approve_edit_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}approve_edit stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Approve and apply a previously validated edit from a dry run with edit_file_lines call using its stateId. It is categorised as a Write tool in the Edit File Lines MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Edit File Lines MCP Server MCP server in PolicyLayer and add a rule for approve_edit: 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 Edit File Lines MCP Server. Nothing to install.
approve_edit 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 approve_edit 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 approve_edit. 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.
approve_edit is provided by the Edit File Lines MCP Server MCP server (oakenai/mcp-edit-file-lines). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Edit File Lines MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 Edit File Lines MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.