Overwrite the entire content of a file. Creates the file if it does not exist.
AI agents use put_content to create or update resources in Obsidian Modified — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian Modified environment.
This tool replaces the full content of a file, which is a destructive-in-practice write operation. However, since it can create files and overwrite (not delete) them, and overwrites are technically reversible if backups exist (Obsidian has version history/sync), Write is the most appropriate category.
From the tool's definition 'Overwrite the entire content of a file. Creates the file if it does not exist.'
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Overwrite the entire content of a file. Creates the file if it does not exist. It is categorised as a Write tool in the Obsidian Modified MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian Modified MCP server in PolicyLayer and add a rule for put_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 Obsidian Modified. Nothing to install.
put_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 put_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 put_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.
put_content is provided by the Obsidian Modified MCP server (@marwansaab/obsidian-modified-mcp-server). 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 →