Append content to a new or existing file in the vault.
AI agents use append_content to create or update resources in MCP server for Obsidian — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP server for Obsidian environment.
This tool adds content to files (creating new ones or extending existing ones), which is a reversible write operation. It does not delete or overwrite data, so it falls under Write rather than Destructive. Medium severity because an AI agent could pollute or corrupt vault notes, but data is recoverable.
From the tool's definition Append content to a new or existing file in the vault
Documented attack patterns abuse exactly the kind of access append_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP server for Obsidian, and nothing reaches the server without passing your rules. This is the rule we recommend for append_content:
{
"version": "1",
"default": "deny",
"tools": {
"append_content": {
"limits": [
{
"counter": "append_content_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} append_content 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.
Append content to a new or existing file in the vault. It is categorised as a Write tool in the MCP server for Obsidian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP server for Obsidian MCP server in PolicyLayer and add a rule for append_content: 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 MCP server for Obsidian. Nothing to install.
append_content 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 append_content 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 append_content. 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.
append_content is provided by the MCP server for Obsidian MCP server (markuspfundstein/mcp-obsidian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP server for Obsidian, 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.
7 MCP server for Obsidian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.