AI agents use create_remix to create or update resources in DramaCraft — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DramaCraft environment.
This tool creates new video files by remixing/compiling existing short drama content. While it modifies/creates data, the operation is reversible (the created video can be deleted or overwritten). It does not delete data irreversibly (ruling out Destructive) nor execute arbitrary code (ruling out Execute).
From the tool's definition Tool name 'create_remix' and description '创建短剧混剪/合集视频' (create short drama remix/compilation video) indicate creation of new video content. The description explicitly uses '创建' (create), which is a Write operation that generates new media assets.
Documented attack patterns abuse exactly the kind of access create_remix 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 create_remix:
{
"version": "1",
"default": "deny",
"tools": {
"create_remix": {
"limits": [
{
"counter": "create_remix_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_remix 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.
Free to start. No card required.
创建短剧混剪/合集视频. It is categorised as a Write tool in the DramaCraft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DramaCraft MCP server in PolicyLayer and add a rule for create_remix: 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.
create_remix 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 create_remix 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 create_remix. 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.
create_remix 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.