flowpass_run

SERVERUnClick SOURCE@unclick/mcp-server

High RISK CLASS

Category Execute

Parameters 120 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/flowpass-run.md

WHAT IT DOES

What flowpass_run does on UnClick

AI agents invoke flowpass_run to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`url`	string	—	Alias for target_url
`pack`	object	—	FlowPass pack object
`fixture`	object	—	Public fixture evidence for route, CTA, form, success, failure, navigation, handoff, side channels, timing, and accessibility.
`pack_id`	string	—	Registered FlowPass pack id
`profile`	string	—	Run profile label. Defaults to smoke.
`pack_name`	string	—	Registered FlowPass pack name
`pack_yaml`	string	—	FlowPass YAML pack using plain-English steps
`journey_id`	string	—	Optional journey id override
`target_sha`	string	—	Optional PR or commit SHA for receipt staleness checks
`target_url`	string	—	Target URL for a one-off FlowPass run
`generated_at`	string	—	Optional ISO timestamp for reproducible fixture tests
`journey_kind`	string	—

Parameters from the server's own tool schema.

RISK

Why flowpass_run is rated High

This tool executes a FlowPass testing or validation workflow against fixtures or packs. While the exact nature of the side effects is unclear from the generic terminology ('journey', 'hat outputs'), the core action is to 'run' something with observable outcomes (verdicts, reports, stored state). This is an Execute-category tool rather than Read because it triggers an operation with stored side effects.

From the tool's definition Tool name 'flowpass_run' and description 'Run FlowPass against a public fixture or registered pack' indicates execution of a process or test workflow.

Risk signalsAccepts URL/endpoint input (url) · High parameter count (13 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs flowpass_run 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_run, this is the rule to start with:

flowpass_run Rate-limited

flowpass_run stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "flowpass_run": {
      "limits": [
        {
          "counter": "flowpass_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every flowpass_run call is checked against it from then on.

FAQ

Questions about flowpass_run

What does the flowpass_run tool do? +

Run FlowPass against a public fixture or registered pack. Returns journey readiness, step verdicts, hat outputs, exclusions, and a stored report. Without fixture proof, returns a plan-only receipt instead of pretending a live journey ran. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does flowpass_run accept? +

flowpass_run accepts 12 parameters: url, pack, fixture, pack_id, profile, pack_name, pack_yaml, journey_id, target_sha, target_url, generated_at, journey_kind. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on flowpass_run? +

Register the UnClick MCP server in PolicyLayer and add a rule for flowpass_run: 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.

What risk level is flowpass_run? +

flowpass_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit flowpass_run? +

Yes. Add a rate_limit block to the flowpass_run 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.

How do I block flowpass_run completely? +

Set action: deny in the PolicyLayer policy for flowpass_run. 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.

What MCP server provides flowpass_run? +

flowpass_run 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.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →