studio_job_status
Poll a Studio job such as studio_permission_video. Omit jobId to list jobs. Optional device_id polls a remote Yaver machine.
This record as markdown: /tools/io-github-kivanccakmak-yaver/studio-job-status.md
What studio_job_status does on Yaver
AI agents call studio_job_status to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
jobId | string | — | |
device_id | string | — | Optional owned Yaver device id/name/alias. |
Parameters from the server's own tool schema.
Why studio_job_status is rated Low
The tool retrieves job status information and optionally lists jobs. These are read-only operations with no side effects, no data modification, and no code execution. The ability to query remote devices does not elevate the risk beyond Read category. Low severity reflects minimal blast radius — polling job status cannot cause harm even if misused by an AI agent.
From the tool's definition Tool name includes 'status' and description states 'Poll a Studio job' and 'list jobs' — both read-only query operations with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs studio_job_status 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_job_status, this is the rule to start with:
studio_job_status is read-only, so it stays allowed. 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 studio_job_status call is checked against it from then on.
Questions about studio_job_status
Poll a Studio job such as studio_permission_video. Omit jobId to list jobs. Optional device_id polls a remote Yaver machine. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
studio_job_status accepts 2 parameters: jobId, device_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 studio_job_status: 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.
studio_job_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the studio_job_status 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 studio_job_status. 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.
studio_job_status 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.
This server
Across the catalogue