flowpass_record
Convert supplied rrweb or structured session events into a draft FlowPass pack. This safe MCP surface does not start a live browser recording by itself.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/flowpass-record.md
What flowpass_record does on UnClick
AI agents use flowpass_record 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 |
|---|---|---|---|
target_url | string | Yes | Target URL the recording or session events came from |
session_events | array | — | Structured event summaries or pre-captured rrweb-derived step labels |
Parameters from the server's own tool schema.
Why flowpass_record is rated Medium
The tool takes input data (session events) and creates a new artifact (a draft FlowPass pack), which is a Write operation. It does not execute code or a live browser session ('does not start a live browser recording by itself'), nor does it delete data or involve finances. The severity is medium because it processes potentially sensitive session/interaction recordings into a structured pack.
From the tool's definition "Convert supplied rrweb or structured session events into a draft FlowPass pack"
Attacks that exploit this kind of access
The rule that runs flowpass_record 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_record, this is the rule to start with:
flowpass_record 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_record call is checked against it from then on.
Questions about flowpass_record
Convert supplied rrweb or structured session events into a draft FlowPass pack. This safe MCP surface does not start a live browser recording by itself. 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_record accepts 2 parameters: target_url, session_events. Required: target_url. 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_record: 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_record 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_record 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_record. 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_record 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