variant_pack
Generate N perturbed variants around an anchor parameter look and write the whole pack to the Obsidian vault as a morph_pack-compatible JSON. Probes the target COMP
This record as markdown: /tools/hybridlabor-api-aos/variant-pack.md
What variant_pack does on Aos
AI agents use variant_pack 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 variant_pack is rated Medium
The tool creates multiple perturbed variants (generative/transformative operation) and explicitly writes them to persistent storage (Obsidian vault). This is a Write operation—it modifies the state of the vault by adding new JSON data structures. While it has some Read characteristics (probing the target component), the primary intent and effect is to create and persist new data.
From the tool's definition Tool generates and writes 'the whole pack to the Obsidian vault as...JSON' and 'Probes the target COMP', indicating data creation and modification operations that persist to storage.
Attacks that exploit this kind of access
The rule that runs variant_pack 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 variant_pack, this is the rule to start with:
variant_pack 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 variant_pack call is checked against it from then on.
Questions about variant_pack
Generate N perturbed variants around an anchor parameter look and write the whole pack to the Obsidian vault as a morph_pack-compatible JSON. Probes the target COMP. 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 variant_pack: 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.
variant_pack 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 variant_pack 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 variant_pack. 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.
variant_pack 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