AI agents use merge_videos_tool to create or update resources in Vedit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vedit environment.
Merging videos typically creates a new combined video file (Write category). It is unlikely to be Destructive since merging usually produces a new output without necessarily deleting sources. However, the empty description means we cannot confirm behavior, so confidence is reduced. Severity is medium given the potential to overwrite existing files if output paths conflict.
From the tool's definition Tool name 'merge_videos_tool' suggests combining multiple video files into one, which is a write/create operation. Description is empty, lowering confidence.
Attacks that exploit this kind of access
merge_videos_tool. It is categorised as a Write tool in the Vedit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vedit MCP server in PolicyLayer and add a rule for merge_videos_tool: 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 Vedit. Nothing to install.
merge_videos_tool 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 merge_videos_tool 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 merge_videos_tool. 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.
merge_videos_tool is provided by the Vedit MCP server (zakahan/vedit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →