Suggest frontmatter fields for a note based on folder-conventions, wikilink-neighborhood, and title/body content-heuristics. Returns {existing, suggestions, conflicts}. Two input modes: (1) existing note via {path}; (2) draft via {content, folder_hint, title}. At least one of path/content require...
AI agents call suggest_frontmatter to retrieve information from Vault Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read/analysis tool that examines note metadata and content to propose frontmatter improvements, with no side effects. It retrieves and analyzes data from existing notes or draft content but does not modify, execute, delete, or perform financial operations. The low severity reflects that misuse would only surface unhelpful suggestions without causing harm.
From the tool's definition Tool returns suggestions and analysis ({existing, suggestions, conflicts}) based on note content and conventions. The description uses analytical verbs: 'Suggest', 'Returns', 'Suggestions sorted by confidence'.
Attacks that exploit this kind of access
Suggest frontmatter fields for a note based on folder-conventions, wikilink-neighborhood, and title/body content-heuristics. Returns {existing, suggestions, conflicts}. Two input modes: (1) existing note via {path}; (2) draft via {content, folder_hint, title}. At least one of path/content required. Suggestions sorted by confidence DESC; conflicts list disagreements between sources. It is categorised as a Read tool in the Vault Memory MCP Server, which means it retrieves data without modifying state.
Register the Vault Memory MCP server in PolicyLayer and add a rule for suggest_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 Vault Memory. Nothing to install.
suggest_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 suggest_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 suggest_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.
suggest_frontmatter is provided by the Vault Memory MCP server (owrede/vault-memory). 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 →