add_tags_tool
AI agents use add_tags_tool to create or update resources in Obsidian MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian MCP Server environment.
Adding tags to notes modifies metadata reversibly—tags can be added, removed, or edited without permanently destroying content. This is a Write operation. Severity is medium because bulk tag operations could inadvertently reorganize or mislabel significant portions of a vault, affecting discoverability and organization, but the changes are not destructive and can be undone.
From the tool's definition Tool name 'add_tags_tool' indicates modification of tag metadata on notes. Sibling tools include 'batch_update_properties_tool', 'edit_note_section_tool', and 'create_note_tool', all Write-category operations.
Attacks that exploit this kind of access
add_tags_tool. It is categorised as a Write tool in the Obsidian MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for add_tags_tool: 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.
add_tags_tool 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 add_tags_tool 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 add_tags_tool. 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.
add_tags_tool is provided by the Obsidian MCP Server MCP server (suhailnajeeb/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 →