obsidian_get_frontmatter
AI agents call obsidian_get_frontmatter to retrieve information from Obsidian MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Frontmatter access is a read operation that retrieves metadata (YAML/TOML headers) from note files without modifying or deleting any content. This matches the 'Read' category profile of querying or retrieving data with no side effects. Low severity due to limited blast radius—metadata exposure is generally less sensitive than file content deletion or arbitrary code execution.
From the tool's definition Tool name 'obsidian_get_frontmatter' indicates retrieval of frontmatter metadata from Obsidian notes. The sibling tools include read operations (obsidian_get_file_contents, obsidian_get_notes_info, obsidian_list_files_in_vault) and write/destructive…
Attacks that exploit this kind of access
obsidian_get_frontmatter. It is categorised as a Read tool in the Obsidian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for obsidian_get_frontmatter: 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.
obsidian_get_frontmatter is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the obsidian_get_frontmatter 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 obsidian_get_frontmatter. 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.
obsidian_get_frontmatter is provided by the Obsidian MCP Server MCP server (shepherd-creative/obsidian-mcp). 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 →