Get the complete tag taxonomy configuration showing allowed tags and restrictions
AI agents call get_tag_taxonomy to retrieve information from Obsidian Ai Curator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of existing tag taxonomy configuration. It retrieves and displays metadata about tags without creating, modifying, deleting, or executing any operations. The sole purpose is to fetch and present information about the system's tag structure, which is a low-severity read operation.
From the tool's definition The tool 'get_tag_taxonomy' retrieves configuration data by 'showing allowed tags and restrictions' with no mention of modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_tag_taxonomy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Ai Curator, and nothing reaches the server without passing your rules. This is the rule we recommend for get_tag_taxonomy:
{
"version": "1",
"default": "deny",
"tools": {
"get_tag_taxonomy": {}
}
}get_tag_taxonomy is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the complete tag taxonomy configuration showing allowed tags and restrictions. It is categorised as a Read tool in the Obsidian Ai Curator MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Ai Curator MCP server in PolicyLayer and add a rule for get_tag_taxonomy: 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 Ai Curator. Nothing to install.
get_tag_taxonomy 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_tag_taxonomy 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_tag_taxonomy. 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_tag_taxonomy is provided by the Obsidian Ai Curator MCP server (nwant/obsidian-ai-curator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian Ai Curator, 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.
27 Obsidian Ai Curator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.