Skip to content

execute_template

Run a Templater template and write the expanded output to a target path. Returns the vault-relative path Templater actually created. Always requires human confirmation (write:templater is a HITL floor) because templates can execute arbitrary user JavaScript. Domain: automation.

Domain automation
Scopes write:templater
Access write
Tags writes, hitl, plugin-bridge, domain:automation
Profile full only
Annotation Value
Read-only no
Destructive no
Idempotent no
Accepts an idempotency key no

Idempotent is the advisory MCP idempotentHint. Destructive is also yes for a tool that asks for confirmation only on some calls.

A single-use elicit_token (or a transport-verified confirmation) is required on every call.

  • The confirmation binds to the vault paths the call names, which are also checked against the folder ACL.
Parameter Type Required Default Description
vault string — Vault id. May be omitted when only one vault is available. length 1–64; pattern ^[a-z0-9_-]+$
template string yes — length 1–1024
target string yes — length 1–1024
args Record<string, any> — —
overwrite boolean false —
Field Type Always present Description
vault string yes —
template string yes —
target string yes —
created_at string yes —
content_hash string —
provenance_stamp object —
provenance_stamp.applied boolean with parent —
provenance_stamp.reason enum with parent One of: "concurrent_modification"

Other tools in the automation domain: bundle_files, bundle_folder, eval_dataview_field, execute_command, generate_uri, list_commands, list_quickadd_actions, list_tasks, list_templates, makemd_list_spaces, makemd_query, remotely_save_status, remotely_save_trigger, show_file_in_obsidian, tasks_filter, trigger_quickadd, update_task, validate_dql.

Back to the tool catalog.