Parse and return the YAML frontmatter of a note as key-value pairs.
AI agents call get_frontmatter to retrieve information from Mcp Obsidian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and parses existing metadata from a note without creating, modifying, deleting, or executing any operations. It is a pure data retrieval operation, making it a Read category tool with low severity since it merely exposes note metadata without enabling further actions.
From the tool's definition The tool 'get_frontmatter' is described as parsing and returning YAML frontmatter as key-value pairs. The verb 'return' and the function of retrieving metadata from an existing note indicate a read-only operation with no side effects.
Attacks that exploit this kind of access
Parse and return the YAML frontmatter of a note as key-value pairs. It is categorised as a Read tool in the Mcp Obsidian MCP Server, which means it retrieves data without modifying state.
Register the Mcp Obsidian MCP server in PolicyLayer and add a rule for 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 Mcp Obsidian. Nothing to install.
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 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 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.
get_frontmatter is provided by the Mcp Obsidian MCP server (jkang8/mcp-obsidian). 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 →