tag_and_search_library
Faceted browse + tag editing over a vault library (Recipes/ + Components/ markdown notes).
This record as markdown: /tools/hybridlabor-api-aos/tag-and-search-library.md
What tag_and_search_library does on Aos
AI agents use tag_and_search_library to create or update resources in Aos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aos environment.
Why tag_and_search_library is rated Medium
The tool supports both reading (faceted browse/search) and writing (tag editing). Since tag editing modifies stored data, the most severe applicable category is Write. Blast radius is medium: misuse could corrupt or pollute library metadata, but changes are likely reversible.
From the tool's definition 'tag editing over a vault library' — the tool modifies tags on library entries (markdown notes in Recipes/ and Components/)
Attacks that exploit this kind of access
The rule that runs tag_and_search_library safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tag_and_search_library, this is the rule to start with:
tag_and_search_library 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every tag_and_search_library call is checked against it from then on.
Questions about tag_and_search_library
Faceted browse + tag editing over a vault library (Recipes/ + Components/ markdown notes). It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aos MCP server in PolicyLayer and add a rule for tag_and_search_library: 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 Aos. Nothing to install.
tag_and_search_library 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 tag_and_search_library 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 tag_and_search_library. 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.
tag_and_search_library is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue