Make line-based edits to a text file. Each edit replaces a line range with new content (which may span any number of lines). Edits are applied in reverse line order so indices stay stable. Returns a git-style diff. Only works within allowed directories.
AI agents use edit_file to create or update resources in FilesystemMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FilesystemMCP environment.
This tool creates or modifies data reversibly, fitting the Write category. It is not Destructive because edits are line-based replacements (reversible via version control or undo) rather than irreversible deletion.
From the tool's definition Tool description explicitly states 'Make line-based edits to a text file' and 'Each edit replaces a line range with new content.' The tool modifies file content reversibly (can be undone), and returns a git-style diff showing changes.
Attacks that exploit this kind of access
Make line-based edits to a text file. Each edit replaces a line range with new content (which may span any number of lines). Edits are applied in reverse line order so indices stay stable. Returns a git-style diff. Only works within allowed directories. It is categorised as a Write tool in the FilesystemMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Filesystem MCP server in PolicyLayer and add a rule for edit_file: 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 FilesystemMCP. Nothing to install.
edit_file 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 edit_file 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 edit_file. 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.
edit_file is provided by the Filesystem MCP server (rijadalisic/filesystemmcp). 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 →