AI agents use export_to_jianying 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 is a Write operation because it creates or sends data to an external system (Jianying/CapCut) in a specific format. The severity is medium because while it modifies data in an external system, it is reversible (the exported project can be deleted or modified), and the blast radius is limited to the video editing project itself rather than affecting core business data or financial systems.
From the tool's definition Tool name 'export_to_jianying' and description '导出项目到剪映格式' (export project to Jianying format) indicates the tool exports/writes data to an external video editing platform (CapCut/Jianying).
Documented attack patterns abuse exactly the kind of access export_to_jianying 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 export_to_jianying:
{
"version": "1",
"default": "deny",
"tools": {
"export_to_jianying": {
"limits": [
{
"counter": "export_to_jianying_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_to_jianying 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 export_to_jianying: 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.
export_to_jianying 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 export_to_jianying 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 export_to_jianying. 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.
export_to_jianying 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.