This record as markdown: /tools/io-github-kivanccakmak-yaver/stop-task.md
What stop_task does on Yaver
AI agents invoke stop_task 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 |
|---|---|---|---|
task_id | string | Yes | The task ID to stop |
Parameters from the server's own tool schema.
Why stop_task is rated High
Stopping a task is an active operation that triggers external effects (halting a process), making it Execute rather than Read or Write. It is not Destructive (data is not deleted/overwritten), not Financial, and not merely informational. Severity is medium because interrupting a task could disrupt development workflows or ongoing operations, but the impact is typically reversible by restarting.
From the tool's definition Tool name 'stop_task' and description 'Stop a running task' indicates termination of an executing process or operation.
Attacks that exploit this kind of access
The rule that runs stop_task 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 stop_task, this is the rule to start with:
stop_task 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 stop_task call is checked against it from then on.
Questions about stop_task
Stop a running task. 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.
stop_task accepts 1 parameter: task_id. Required: task_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 stop_task: 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.
stop_task 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 stop_task 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 stop_task. 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.
stop_task 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