Capture the current frame from a robot/machine cell's camera and return it as a VIEWABLE image, so you (the host model) can SEE the workspace and do vision-in-the-loop robotics development: write code → move the robot (ops robot_move/robot_jog) → look → fix. Targets any device on the mesh via mac...
AI agents use robot_camera 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
machine | string | — | Target cell: "local", "primary", or a deviceId / alias. Default "local". |
Parameters from the server's own tool schema.
An AI agent can call robot_camera 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
Capture the current frame from a robot/machine cell's camera and return it as a VIEWABLE image, so you (the host model) can SEE the workspace and do vision-in-the-loop robotics development: write code → move the robot (ops robot_move/robot_jog) → look → fix. Targets any device on the mesh via machine (e.g. an Android phone wired next to an Ender/Fairino). The cell needs a camera: local /dev/video0, an http(s):// snapshot URL, or an "external" push buffer the box fills with its OWN camera. For the box's on-device vision model instead, use ops verb robot_look. 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.
robot_camera accepts 1 parameter: machine. 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 robot_camera: 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.
robot_camera is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the robot_camera 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 robot_camera. 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.
robot_camera 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.