分割视频文件，支持按时长、大小或段数分割
AI agents call splitVideo to retrieve information from Video Clip MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though splitVideo 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.
Attacks that exploit this kind of access
分割视频文件，支持按时长、大小或段数分割. It is categorised as a Read tool in the Video Clip MCP MCP Server, which means it retrieves data without modifying state.
Register the Video Clip MCP server in PolicyLayer and add a rule for splitVideo: 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 Video Clip MCP. Nothing to install.
splitVideo 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 splitVideo 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 splitVideo. 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.
splitVideo is provided by the Video Clip MCP server (pickstar-2002/video-clip-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
splitVideo is one line of Video Clip's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →