flowpass_disagreement_queue
List or resolve FlowPass Driver versus Verifier disagreements.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/flowpass-disagreement-queue.md
What flowpass_disagreement_queue does on UnClick
AI agents use flowpass_disagreement_queue 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 |
run_id | string | — | Optional FlowPass run id to filter |
reviewer_note | string | — | Human note for disagreement resolution |
disagreement_id | string | — | Disagreement id for resolve |
Parameters from the server's own tool schema.
Why flowpass_disagreement_queue is rated Medium
The tool has dual functionality: listing (Read) and resolving (Write) disagreements. Per the rules, the most severe applicable category wins. Resolving a disagreement changes its state, making this a Write operation. Severity is medium because resolving workflow disagreements could have meaningful business impact if misused, though it is reversible in principle.
From the tool's definition 'List or resolve FlowPass Driver versus Verifier disagreements' — the resolve action modifies/updates the state of disagreement records
Attacks that exploit this kind of access
The rule that runs flowpass_disagreement_queue 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_disagreement_queue, this is the rule to start with:
flowpass_disagreement_queue 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_disagreement_queue call is checked against it from then on.
Questions about flowpass_disagreement_queue
List or resolve FlowPass Driver versus Verifier disagreements. 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_disagreement_queue accepts 4 parameters: action, run_id, reviewer_note, disagreement_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_disagreement_queue: 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_disagreement_queue 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_disagreement_queue 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_disagreement_queue. 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_disagreement_queue 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