uxpass_register_pack
Register a UXPass pack from a YAML string. Validates the basic shape (required keys: name, url, viewports, themes, hats, synthesiser, budgets, remediation) and persists the pack so uxpass_run can reference it by name. Returns the assigned pack_id.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/uxpass-register-pack.md
What uxpass_register_pack does on UnClick
AI agents use uxpass_register_pack to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
pack_yaml | string | Yes | Full pack definition as a YAML string |
Parameters from the server's own tool schema.
Why uxpass_register_pack is rated Medium
This tool creates and stores a new UXPass pack configuration in a system, modifying the persisted state of the service. While it doesn't execute arbitrary commands or delete data, it does write configuration that could affect downstream operations (as indicated by the reference to 'uxpass_run can reference it by name').
From the tool's definition Tool persists data ('persists the pack') and creates a new resource ('assigned pack_id') based on YAML input. The verb 'Register' and the action of storing configuration implies data creation/modification.
Attacks that exploit this kind of access
The rule that runs uxpass_register_pack safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For uxpass_register_pack, this is the rule to start with:
uxpass_register_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 UnClick, apply this rule, and every uxpass_register_pack call is checked against it from then on.
Questions about uxpass_register_pack
Register a UXPass pack from a YAML string. Validates the basic shape (required keys: name, url, viewports, themes, hats, synthesiser, budgets, remediation) and persists the pack so uxpass_run can reference it by name. Returns the assigned pack_id. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
uxpass_register_pack accepts 1 parameter: pack_yaml. Required: pack_yaml. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for uxpass_register_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 UnClick. Nothing to install.
uxpass_register_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 uxpass_register_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 uxpass_register_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.
uxpass_register_pack is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue