flowpass_status
Fetch the stored FlowPass run status, score, summary, and open disagreement queue entries for a run started in this MCP session.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/flowpass-status.md
What flowpass_status does on UnClick
AI agents call flowpass_status to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
run_id | string | Yes | The FlowPass run id returned by flowpass_run |
Parameters from the server's own tool schema.
Why flowpass_status is rated Low
This tool retrieves and queries previously stored FlowPass run data within the current session. It has no capability to modify, delete, or execute operations. The action is purely informational retrieval, which fits the Read category at low severity due to minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'Fetch the stored FlowPass run status, score, summary, and open disagreement queue entries' — uses the verb 'Fetch', indicating data retrieval only. No side effects, modifications, deletions, or external operations are implied.
Attacks that exploit this kind of access
The rule that runs flowpass_status 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_status, this is the rule to start with:
flowpass_status is read-only, so it stays allowed. 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_status call is checked against it from then on.
Questions about flowpass_status
Fetch the stored FlowPass run status, score, summary, and open disagreement queue entries for a run started in this MCP session. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
flowpass_status accepts 1 parameter: run_id. Required: run_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_status: 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_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the flowpass_status 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_status. 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_status 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