Get the frontmatter metadata and tags from a note
AI agents call get_note_metadata 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.
This tool retrieves metadata and tags from an existing note without creating, modifying, deleting, or executing anything. It is a read-only query operation against note metadata, similar to other Read category tools on this server like 'read_note' and 'list_notes'. The blast radius is minimal—misuse would only expose information already in the user's vault, not alter or delete data.
From the tool's definition Tool name 'get_note_metadata' and description 'Get the frontmatter metadata and tags from a note' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get the frontmatter metadata and tags from a note. 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 get_note_metadata: 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.
get_note_metadata 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_note_metadata 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_note_metadata. 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_note_metadata is provided by the Obsidian MCP Server MCP server (markheramis/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 →