The vault to read from.
One of path or title is required. key narrows the
response to a single value.
Full-map or keyed response. A missing keyed value is explicit null.
Trust boundary — this is an in-process API that trusts its
key argument's length. The MCP boundary (obsidian_frontmatter_get in
tool-registry.ts) caps key at MAX_FRONTMATTER_KEY_LEN (256, rc.13
AUD-04) so a remote bearer client cannot drive an unbounded multi-MB key
through the per-note lookupFoldedKey fold; direct internal callers are
not capped and must pass sane keys.
Read a note's frontmatter — full map, or a single key's value.
The read-only counterpart to frontmatterSet (write side). Use this
before bulk-editing frontmatter so the agent can reason about current
state before issuing a write. When key is set, the response contains only
that key/value projection; it does not duplicate the complete map.
The vault to read from.
One of path or title is required. key narrows the
response to a single value.
Full-map or keyed response. A missing keyed value is explicit null.
Trust boundary — this is an in-process API that trusts its
key argument's length. The MCP boundary (obsidian_frontmatter_get in
tool-registry.ts) caps key at MAX_FRONTMATTER_KEY_LEN (256, rc.13
AUD-04) so a remote bearer client cannot drive an unbounded multi-MB key
through the per-note lookupFoldedKey fold; direct internal callers are
not capped and must pass sane keys.
Read a note's frontmatter — full map, or a single key's value.
The read-only counterpart to frontmatterSet (write side). Use this
before bulk-editing frontmatter so the agent can reason about current
state before issuing a write. When key is set, the response contains only
that key/value projection; it does not duplicate the complete map.
The vault to read from.
One of path or title is required. key narrows the
response to a single value.
Full-map or keyed response. A missing keyed value is explicit null.
Trust boundary — this is an in-process API that trusts its
key argument's length. The MCP boundary (obsidian_frontmatter_get in
tool-registry.ts) caps key at MAX_FRONTMATTER_KEY_LEN (256, rc.13
AUD-04) so a remote bearer client cannot drive an unbounded multi-MB key
through the per-note lookupFoldedKey fold; direct internal callers are
not capped and must pass sane keys.
Read a note's frontmatter — full map, or a single key's value.
The read-only counterpart to
frontmatterSet(write side). Use this before bulk-editing frontmatter so the agent can reason about current state before issuing a write. Whenkeyis set, the response contains only that key/value projection; it does not duplicate the complete map.