list_runs
Call this tool when the user wants a recent history of Crews runs. Returns a ConversationalCard with a run count and the newest few run ids.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/list-runs.md
What list_runs does on UnClick
AI agents call list_runs 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 |
|---|---|---|---|
limit | number | — | Optional: max rows to return (default 50, capped at 100) |
crew_id | string | — | Optional: filter to one crew |
Parameters from the server's own tool schema.
Why list_runs is rated Low
This tool queries and retrieves historical metadata about past runs without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal security risk—it only exposes historical run information that may already be accessible through other means. The blast radius of misuse is limited to information disclosure.
From the tool's definition Tool description states it 'Returns a ConversationalCard with a run count and the newest few run ids' — a pure retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_runs 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 list_runs, this is the rule to start with:
list_runs 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 list_runs call is checked against it from then on.
Questions about list_runs
Call this tool when the user wants a recent history of Crews runs. Returns a ConversationalCard with a run count and the newest few run ids. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
list_runs accepts 2 parameters: limit, crew_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 list_runs: 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.
list_runs 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 list_runs 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 list_runs. 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.
list_runs 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