obsidian-mcp-upsert-file
AI agents use obsidian-mcp-upsert-file to create or update resources in Vault MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vault MCP environment.
Upsert is a reversible write operation that creates new files or modifies existing ones. It does not delete or destroy data (thus not Destructive), does not execute arbitrary code (thus not Execute), and causes no financial impact.
From the tool's definition Tool name 'upsert-file' indicates creation or modification of files (upsert = update or insert). Server context confirms 'file management' capabilities.
Documented attack patterns abuse exactly the kind of access obsidian-mcp-upsert-file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vault MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for obsidian-mcp-upsert-file:
{
"version": "1",
"default": "deny",
"tools": {
"obsidian-mcp-upsert-file": {
"limits": [
{
"counter": "obsidian-mcp-upsert-file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}obsidian-mcp-upsert-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.
obsidian-mcp-upsert-file. It is categorised as a Write tool in the Vault MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vault MCP server in PolicyLayer and add a rule for obsidian-mcp-upsert-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 Vault MCP. Nothing to install.
obsidian-mcp-upsert-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 obsidian-mcp-upsert-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 obsidian-mcp-upsert-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.
obsidian-mcp-upsert-file is provided by the Vault MCP server (jlevere/obsidian-mcp-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vault 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.
8 Vault MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.