flowpass_register_pack
Register a FlowPass pack from YAML or an object. Validates plain-English steps, hats, assertions, and optional fixture evidence.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/flowpass-register-pack.md
What flowpass_register_pack does on UnClick
AI agents use flowpass_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 | object | — | FlowPass pack object |
overwrite | boolean | — | Allow replacing an existing pack id |
pack_yaml | string | — | FlowPass YAML pack |
Parameters from the server's own tool schema.
Why flowpass_register_pack is rated Medium
This tool creates/registers a new FlowPass pack (workflow configuration), which modifies system state reversibly. It does not execute arbitrary code or delete data, so it falls under Write rather than Execute or Destructive. Severity is medium because misuse could register malicious workflow packs that affect downstream automation, though the impact depends on how those packs are subsequently used.
From the tool's definition Tool description states 'Register a FlowPass pack' — register implies creating or adding a new entry to a system.
Attacks that exploit this kind of access
The rule that runs flowpass_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 flowpass_register_pack, this is the rule to start with:
flowpass_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 flowpass_register_pack call is checked against it from then on.
Questions about flowpass_register_pack
Register a FlowPass pack from YAML or an object. Validates plain-English steps, hats, assertions, and optional fixture evidence. 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.
flowpass_register_pack accepts 3 parameters: pack, overwrite, 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 flowpass_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.
flowpass_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 flowpass_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 flowpass_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.
flowpass_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