update_video_project
Update project-level fields (name, theme, customColors, fps, width, height). Does NOT touch scenes.
This record as markdown: /tools/cloud-easybits-easybits/update-video-project.md
What update_video_project does on EasyBits
AI agents use update_video_project 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 update_video_project is rated Medium
Modifies video project metadata reversibly without deleting or executing external code.
From the tool's definition Update project-level fields: name, theme, customColors, fps, width, height.
Attacks that exploit this kind of access
The rule that runs update_video_project 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 update_video_project, this is the rule to start with:
update_video_project 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 update_video_project call is checked against it from then on.
Questions about update_video_project
Update project-level fields (name, theme, customColors, fps, width, height). Does NOT touch scenes. 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 update_video_project: 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.
update_video_project 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 update_video_project 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 update_video_project. 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.
update_video_project 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