record_drivers · Yaver MCP: Risk & Policy

WHAT IT DOES

What record_drivers does on Yaver

AI agents use record_drivers to create or update resources in Yaver — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

WHY IT NEEDS A POLICY

Why record_drivers needs a policy

An AI agent can call record_drivers faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_drivers Rate-limited

record_drivers stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_drivers": {
      "limits": [
        {
          "counter": "record_drivers_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_drivers

What does the record_drivers tool do? +

Report which screen-recording drivers are available on this host (ffmpeg for macOS/Linux/Windows screen capture, xcrun for iOS Simulator, adb for Android emulator). Use this before record_start so the user knows what install step they may need. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on record_drivers? +

Register the Yaver MCP server in PolicyLayer and add a rule for record_drivers: 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_drivers? +

record_drivers is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit record_drivers? +

Yes. Add a rate_limit block to the record_drivers 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_drivers completely? +

Set action: deny in the PolicyLayer policy for record_drivers. 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_drivers? +

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