Headless-filesystem tag management for YAML frontmatter tags, inline Markdown tags, and local tag index.
AI agents use obsidian_manage_tags to create or update resources in Optimike Obsidian MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Optimike Obsidian MCP environment.
Tag management inherently involves creating, adding, or modifying tags in frontmatter and inline Markdown, which are reversible write operations. While tags can be removed (potentially destructive), the tool's primary function as described is management (add/modify/update), not irreversible deletion.
From the tool's definition Tool description states it performs 'tag management' for 'YAML frontmatter tags, inline Markdown tags, and local tag index,' which involves modifying metadata and index structures within notes.
Documented attack patterns abuse exactly the kind of access obsidian_manage_tags gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Optimike Obsidian MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for obsidian_manage_tags:
{
"version": "1",
"default": "deny",
"tools": {
"obsidian_manage_tags": {
"limits": [
{
"counter": "obsidian_manage_tags_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}obsidian_manage_tags stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Headless-filesystem tag management for YAML frontmatter tags, inline Markdown tags, and local tag index. It is categorised as a Write tool in the Optimike Obsidian MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Optimike Obsidian MCP server in PolicyLayer and add a rule for obsidian_manage_tags: 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 Optimike Obsidian MCP. Nothing to install.
obsidian_manage_tags is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the obsidian_manage_tags 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_manage_tags. 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_manage_tags is provided by the Optimike Obsidian MCP server (optimikelabs/optimike-obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Optimike Obsidian MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Optimike Obsidian MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.