runner_queue_list
List queued prompts. sessionName filters; empty returns every session.
This record as markdown: /tools/io-github-kivanccakmak-yaver/runner-queue-list.md
What runner_queue_list does on Yaver
AI agents call runner_queue_list to retrieve information from Yaver 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 |
|---|---|---|---|
sessionName | string | — |
Parameters from the server's own tool schema.
Why runner_queue_list is rated Low
This tool retrieves or queries data about queued prompts with optional filtering by sessionName. It has no side effects—it does not create, modify, delete, or execute anything. The optional sessionName parameter for filtering does not change the classification, as the core function remains data retrieval. Severity is low because listing queued items poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'runner_queue_list' and description 'List queued prompts' indicate a query/retrieval operation with no modification or execution of the queued items themselves.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs runner_queue_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For runner_queue_list, this is the rule to start with:
runner_queue_list 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 Yaver, apply this rule, and every runner_queue_list call is checked against it from then on.
Questions about runner_queue_list
List queued prompts. sessionName filters; empty returns every session. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
runner_queue_list accepts 1 parameter: sessionName. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for runner_queue_list: 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 Yaver. Nothing to install.
runner_queue_list 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 runner_queue_list 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 runner_queue_list. 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.
runner_queue_list is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue