This record as markdown: /tools/io-github-kivanccakmak-yaver/jobs-cancel.md
What jobs_cancel does on Yaver
AI agents call jobs_cancel 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 |
|---|---|---|---|
id | string | Yes |
Parameters from the server's own tool schema.
Why jobs_cancel is rated Critical
This tool permanently removes a job from a queue. While not data deletion in the traditional sense, dropping a job is an irreversible action that cannot be undone. It falls under Destructive rather than Write because the effect is removal/cancellation rather than reversible modification.
From the tool's definition 'Drop a pending queue job' — the verb 'drop' indicates irreversible deletion of a queued job. Once dropped, the job cannot be recovered or undone.
Attacks that exploit this kind of access
The rule that runs jobs_cancel 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 jobs_cancel, this is the rule to start with:
jobs_cancel 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 jobs_cancel call is checked against it from then on.
Questions about jobs_cancel
Drop a pending queue job. 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.
jobs_cancel accepts 1 parameter: id. Required: id. 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 jobs_cancel: 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.
jobs_cancel 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 jobs_cancel 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 jobs_cancel. 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.
jobs_cancel 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