write_file
Crea o sobrescribe un archivo Markdown en la bóveda.
This record as markdown: /tools/a2rg-obsidian-mcp/write-file.md
What write_file does on Obsidian
AI agents use write_file to create or update resources in Obsidian, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Ruta relativa del archivo dentro de la bóveda |
content | string | Yes | Contenido Markdown a escribir |
Parameters from the server's own tool schema.
Why write_file is rated Medium
An AI agent can call write_file faster than any human can review: one bad instruction and it creates or modifies resources in Obsidian by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs write_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Obsidian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For write_file, this is the rule to start with:
write_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Obsidian, apply this rule, and every write_file call is checked against it from then on.
Questions about write_file
Crea o sobrescribe un archivo Markdown en la bóveda. It is categorised as a Write tool in the Obsidian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
write_file accepts 2 parameters: path, content. Required: path, content. The full parameter table on this page comes from the server's own tool schema.
Register the Obsidian MCP server in PolicyLayer and add a rule for write_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. Nothing to install.
write_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 write_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 write_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.
write_file is provided by the Obsidian MCP server (@a2rg/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Obsidian, and thousands of servers like it.
This server
Across the catalogue