studio_permission_video

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 120 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/studio-permission-video.md

WHAT IT DOES

What studio_permission_video does on Yaver

AI agents invoke studio_permission_video 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
`apk`	string	—	APK path on the target machine, built for the Redroid architecture.
`app`	string	—	App display name.
`path`	string	—	Repo/app root on the target machine.
`what`	string	—	Use case summary.
`image`	string	—
`maxSec`	number	—
`package`	string	—	Android package id, e.g. io.yaver.mobile.
`sshHost`	string	—	Optional on-prem Redroid host reachable from the target machine.
`sshOpts`	string	—
`useCase`	object	—	Narrative driver config: {whatRuns,startButtonText,stopButtonText,progressText,completionText,taskActions[]}.
`activity`	string	—	Launch activity, default .MainActivity.
`manifest`	string	—	AndroidManifest.xml path for static analysis.

Parameters from the server's own tool schema.

RISK

Why studio_permission_video is rated High

This tool executes a complex workflow (video job creation and orchestration on Android emulators/devices) whose effects depend on arguments (device_id, job parameters). While not immediately destructive or financial, it triggers external operations and processes that cannot be trivially rolled back.

From the tool's definition Tool description states it 'Start[s] a Redroid-backed Google Play permission-justification video job' and 'start real work, show it running, background the app, show completion notification, stop.' This indicates execution of automated video generation…

Risk signalsAccepts file system path (path) · High parameter count (17 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs studio_permission_video 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 studio_permission_video, this is the rule to start with:

studio_permission_video Rate-limited

studio_permission_video 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": {
    "studio_permission_video": {
      "limits": [
        {
          "counter": "studio_permission_video_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every studio_permission_video call is checked against it from then on.

FAQ

Questions about studio_permission_video

What does the studio_permission_video tool do? +

Start a Redroid-backed Google Play permission-justification video job. Defaults to a narrative proof: start real work, show it running, background the app, show completion notification, stop. Optional device_id runs on a remote Yaver machine with Docker/Redroid. Poll studio_job_status. 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 studio_permission_video accept? +

studio_permission_video accepts 12 parameters: apk, app, path, what, image, maxSec, package, sshHost, sshOpts, useCase, activity, manifest. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on studio_permission_video? +

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

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

Can I rate-limit studio_permission_video? +

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

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

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

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →