AI agents use render_template to create or update resources in Obsidian MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian MCP Server environment.
Rendering a template with variables typically produces output written to a file or note in the vault. Given the sibling tools (create_note, create_from_template, etc.), this likely creates or modifies content in Obsidian. It is a Write operation since it generates/creates new content, though confidence is moderate because the description is minimal and doesn't specify whether the output is persisted or just returned.
From the tool's definition Render a template with variables
Documented attack patterns abuse exactly the kind of access render_template gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for render_template:
{
"version": "1",
"default": "deny",
"tools": {
"render_template": {
"limits": [
{
"counter": "render_template_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}render_template 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.
Render a template with variables. It is categorised as a Write tool in the Obsidian MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for render_template: 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 MCP Server. Nothing to install.
render_template 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 render_template 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 render_template. 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.
render_template is provided by the Obsidian MCP Server MCP server (bazylhorsey/obsidian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian MCP Server, 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.
29 Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.