set_video_scene
Edit a scene by id (from get_video_project scenes[].id). Only pass the fields you change. Changing narration re-synthesizes the voiceover on next render.
This record as markdown: /tools/cloud-easybits-easybits/set-video-scene.md
What set_video_scene does on EasyBits
AI agents use set_video_scene to create or update resources in EasyBits, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EasyBits environment.
Why set_video_scene is rated Medium
Modifies video scene data reversibly; cannot delete or execute code, but affects rendered output.
From the tool's definition Edit a scene by id. Only pass the fields you change.
Attacks that exploit this kind of access
The rule that runs set_video_scene 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 set_video_scene, this is the rule to start with:
set_video_scene 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.
The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every set_video_scene call is checked against it from then on.
Questions about set_video_scene
Edit a scene by id (from get_video_project scenes[].id). Only pass the fields you change. Changing narration re-synthesizes the voiceover on next render. It is categorised as a Write tool in the EasyBits MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EasyBits MCP server in PolicyLayer and add a rule for set_video_scene: 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.
set_video_scene 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 set_video_scene 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 set_video_scene. 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.
set_video_scene 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.
This server
Across the catalogue