jobs_enqueue
Enqueue a new background job. Handlers are registered at agent boot; common ones: newsletter.send, form.notify, pdf.render.
This record as markdown: /tools/io-github-kivanccakmak-yaver/jobs-enqueue.md
What jobs_enqueue does on Yaver
AI agents invoke jobs_enqueue to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
handler | string | Yes | |
payload | object | — | |
delaySec | integer | — | |
backoffSec | integer | — | |
maxAttempts | integer | — |
Parameters from the server's own tool schema.
Why jobs_enqueue is rated High
Enqueueing a background job triggers execution of external side-effecting operations. Handlers like newsletter.send and form.notify involve sending communications to potentially large numbers of users, making misuse high-severity. The effects are not easily reversible (emails/notifications sent cannot be unsent), though the primary action is executing/triggering rather than destructive deletion.
From the tool's definition 'Enqueue a new background job' with handlers like 'newsletter.send, form.notify, pdf.render' — triggers external operations (sending emails, notifications, rendering)
Risk signalsAccepts raw HTML/template content (payload)
Attacks that exploit this kind of access
The rule that runs jobs_enqueue 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_enqueue, this is the rule to start with:
jobs_enqueue stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 jobs_enqueue call is checked against it from then on.
Questions about jobs_enqueue
Enqueue a new background job. Handlers are registered at agent boot; common ones: newsletter.send, form.notify, pdf.render. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
jobs_enqueue accepts 5 parameters: handler, payload, delaySec, backoffSec, maxAttempts. Required: handler. 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_enqueue: 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_enqueue is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the jobs_enqueue 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_enqueue. 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_enqueue 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