AI agents invoke smart_video_edit to trigger actions in DramaCraft. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool orchestrates multiple sub-operations (analyze, plan, generate draft) in an automated AI-driven pipeline, constituting execution of a complex workflow rather than a simple read or write. It triggers external operations via Jianying/CapCut integration and invokes Chinese LLMs. Misuse could result in unintended video content generation or unwanted drafts being created at scale, hence high severity.
From the tool's definition AI智能视频编辑 - 一键完成分析、规划和草稿生成 ('One-click completion of analysis, planning, and draft generation'); integrates multiple operations including analysis, planning, and draft creation in a single automated pipeline
Documented attack patterns abuse exactly the kind of access smart_video_edit gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DramaCraft, and nothing reaches the server without passing your rules. This is the rule we recommend for smart_video_edit:
{
"version": "1",
"default": "deny",
"tools": {
"smart_video_edit": {
"limits": [
{
"counter": "smart_video_edit_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}smart_video_edit stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
AI智能视频编辑 - 一键完成分析、规划和草稿生成. It is categorised as a Execute tool in the DramaCraft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DramaCraft MCP server in PolicyLayer and add a rule for smart_video_edit: 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 DramaCraft. Nothing to install.
smart_video_edit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the smart_video_edit 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 smart_video_edit. 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.
smart_video_edit is provided by the DramaCraft MCP server (jackyxia918918/dramacraft). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DramaCraft, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 DramaCraft tools catalogued and risk-classified — across an index of 43,000+ MCP servers.