runner_queue_clear
Drop queued prompts (one session or all). Destructive.
This record as markdown: /tools/io-github-kivanccakmak-yaver/runner-queue-clear.md
What runner_queue_clear does on Yaver
AI agents call runner_queue_clear to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
sessionName | string | — |
Parameters from the server's own tool schema.
Why runner_queue_clear is rated Critical
This tool irreversibly deletes queued prompts from either a single session or globally across all sessions. Deletion is permanent and cannot be undone, meeting the definition of Destructive. The blast radius is high because clearing queued work could disrupt active development sessions and cause loss of pending tasks, though the impact is limited to prompt queues rather than source code or production systems.
From the tool's definition Tool name 'runner_queue_clear' and description explicitly states 'Drop queued prompts (one session or all). Destructive.' The verb 'drop' combined with the explicit 'Destructive' label indicates irreversible deletion of queued data.
Attacks that exploit this kind of access
The rule that runs runner_queue_clear 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_clear, this is the rule to start with:
runner_queue_clear is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every runner_queue_clear call is checked against it from then on.
Questions about runner_queue_clear
Drop queued prompts (one session or all). Destructive. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
runner_queue_clear 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_clear: 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_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the runner_queue_clear 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_clear. 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_clear 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.
Across the catalogue