Use this whenever the user asks for the metadata, tags, frontmatter, or properties of a specific note (without reading the body). Returns parsed YAML frontmatter as JSON (title, tags, date, status, etc.). Triggers:
AI agents call garden_tag to retrieve information from Synapse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves structured metadata from note frontmatter. It has no side effects, does not modify data, execute code, or delete anything. The low severity reflects that metadata exposure is generally lower risk than full note content, though sensitive information could theoretically be in frontmatter tags or properties. Confidence is high due to clear, explicit scope in the description.
From the tool's definition Tool returns parsed YAML frontmatter and metadata (title, tags, date, status) without reading the note body. The description explicitly states it retrieves metadata and properties, with no modification or execution capabilities.
Attacks that exploit this kind of access
Use this whenever the user asks for the metadata, tags, frontmatter, or properties of a specific note (without reading the body). Returns parsed YAML frontmatter as JSON (title, tags, date, status, etc.). Triggers:. It is categorised as a Read tool in the Synapse MCP Server, which means it retrieves data without modifying state.
Register the Synapse MCP server in PolicyLayer and add a rule for garden_tag: 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 Synapse. Nothing to install.
garden_tag 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 garden_tag 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 garden_tag. 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.
garden_tag is provided by the Synapse MCP server (tomjrworks/synapse-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 →