record_stop · Yaver MCP: Risk & Policy

WHAT IT DOES

What record_stop does on Yaver

AI agents invoke record_stop 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.

PARAMETERS

Parameter	Type	Required	Description
`run_id`	string	Yes
`task_id`	string	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why record_stop needs a policy

record_stop triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_stop Rate-limited

record_stop 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_stop": {
      "limits": [
        {
          "counter": "record_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about record_stop

What does the record_stop tool do? +

Finalize the recording started for (run_id, task_id). Returns duration_ms + size_bytes. After this the video is served at /recordings/{run_id}/{task_id}/video.mp4 with byte-range support. 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.

What parameters does record_stop accept? +

record_stop accepts 2 parameters: run_id, task_id. Required: run_id, task_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on record_stop? +

Register the Yaver MCP server in PolicyLayer and add a rule for record_stop: 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.

What risk level is record_stop? +

record_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit record_stop? +

Yes. Add a rate_limit block to the record_stop 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.

How do I block record_stop completely? +

Set action: deny in the PolicyLayer policy for record_stop. 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.

What MCP server provides record_stop? +

record_stop 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.