reorder_video_scenes
Reorder all scenes. sceneIds must list every existing scene id exactly once in the desired order.
This record as markdown: /tools/cloud-easybits-easybits/reorder-video-scenes.md
What reorder_video_scenes does on EasyBits
AI agents call reorder_video_scenes to retrieve information from EasyBits without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why reorder_video_scenes is rated Low
Even though reorder_video_scenes only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs reorder_video_scenes 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 reorder_video_scenes, this is the rule to start with:
reorder_video_scenes 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 EasyBits, apply this rule, and every reorder_video_scenes call is checked against it from then on.
Questions about reorder_video_scenes
Reorder all scenes. sceneIds must list every existing scene id exactly once in the desired order. It is categorised as a Read tool in the EasyBits MCP Server, which means it retrieves data without modifying state.
Register the EasyBits MCP server in PolicyLayer and add a rule for reorder_video_scenes: 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.
reorder_video_scenes 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 reorder_video_scenes 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 reorder_video_scenes. 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.
reorder_video_scenes 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