flowpass_quarantine
List, add, or resolve FlowPass quarantines for flows that should not be trusted as gates.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/flowpass-quarantine.md
What flowpass_quarantine does on UnClick
AI agents use flowpass_quarantine 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 |
|---|---|---|---|
action | string | — | Defaults to list |
reason | string | — | Reason when adding a quarantine |
flow_id | string | — | Flow id for add or resolve |
Parameters from the server's own tool schema.
Why flowpass_quarantine is rated Medium
This tool modifies quarantine status of flows (adding or resolving quarantines), which constitutes data modification. While quarantine changes are theoretically reversible (a quarantine can be added or removed), they affect access control and trust decisions for flows. The impact is limited to flow trust status rather than deletion or financial operations, placing it in Write category.
From the tool's definition The tool description states it can 'add, or resolve' quarantines, indicating it modifies quarantine state for flows. The 'list' operation is read-only, but the tool's primary function encompasses reversible write operations.
Attacks that exploit this kind of access
The rule that runs flowpass_quarantine 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_quarantine, this is the rule to start with:
flowpass_quarantine 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_quarantine call is checked against it from then on.
Questions about flowpass_quarantine
List, add, or resolve FlowPass quarantines for flows that should not be trusted as gates. 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_quarantine accepts 3 parameters: action, reason, flow_id. 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_quarantine: 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_quarantine 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_quarantine 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_quarantine. 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_quarantine 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