agent_recording_start
Start recording the desktop of a computer-use agent (computer-ghosty-gemini). ffmpeg captures display :0 to an mp4 inside the VM. One recording at a time per agent; calling again while recording returns the in-progress one. Returns { recording, id, startedAt, url } — the url becomes a playable mp...
This record as markdown: /tools/cloud-easybits-easybits/agent-recording-start.md
What agent_recording_start does on EasyBits
AI agents invoke agent_recording_start to trigger actions in EasyBits. 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.
Why agent_recording_start is rated High
Initiates external recording process with side effects; depends on agent actions for impact.
From the tool's definition Start recording desktop, ffmpeg captures display, drive agent with agent_message
Attacks that exploit this kind of access
The rule that runs agent_recording_start safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agent_recording_start, this is the rule to start with:
agent_recording_start 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.
The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every agent_recording_start call is checked against it from then on.
Questions about agent_recording_start
Start recording the desktop of a computer-use agent (computer-ghosty-gemini). ffmpeg captures display :0 to an mp4 inside the VM. One recording at a time per agent; calling again while recording returns the in-progress one. Returns { recording, id, startedAt, url } — the url becomes a playable mp4 after agent_recording_stop. Drive the agent with agent_message between start and stop, then stop to finalize. It is categorised as a Execute tool in the EasyBits MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the EasyBits MCP server in PolicyLayer and add a rule for agent_recording_start: 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 EasyBits. Nothing to install.
agent_recording_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the agent_recording_start 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 agent_recording_start. 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.
agent_recording_start is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
Across the catalogue