Surgically edit file content using exact string replacement (pattern matching). Use this for arbitrary text edits anywhere in the file. IMPORTANT: old_string must match exactly (including whitespace/indentation). Include enough context to make old_string unique. For structured edits (headings/fro...
AI agents use edit_file to create or update resources in Obsidian HTTP MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian HTTP MCP environment.
The edit_file tool modifies file content reversibly through pattern matching and string replacement. This is a Write operation because changes can theoretically be undone (unlike Destructive operations). Severity is medium because an AI agent misusing this could corrupt note content, but the requirement for exact string matching mitigates some risk.
From the tool's definition Tool description explicitly states 'edit file content' and 'arbitrary text edits' using 'string replacement', enabling modification of file content.
Documented attack patterns abuse exactly the kind of access edit_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian HTTP MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for edit_file:
{
"version": "1",
"default": "deny",
"tools": {
"edit_file": {
"limits": [
{
"counter": "edit_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} edit_file 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.
Surgically edit file content using exact string replacement (pattern matching). Use this for arbitrary text edits anywhere in the file. IMPORTANT: old_string must match exactly (including whitespace/indentation). Include enough context to make old_string unique. For structured edits (headings/frontmatter), consider using patch_file instead (coming soon). It is categorised as a Write tool in the Obsidian HTTP MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian HTTP 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 Obsidian HTTP MCP. 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 Obsidian HTTP MCP server (nasandnora/obsidian-http-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian HTTP MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Obsidian HTTP MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.