Lottie 动画生成：从 34 种预置模板生成自定义 Lottie JSON 动画，支持颜色/尺寸/帧率自定义。
AI agents use qflow_lottie to create or update resources in Qflow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Qflow environment.
This tool creates new animation JSON files based on templates and user parameters. While it modifies/generates data, the effect is reversible (animations can be deleted or recreated), so it falls under Write rather than Destructive. The blast radius is minimal—misconfigured animation parameters would only result in unwanted animation output that can be easily discarded.
From the tool's definition Generates and creates custom Lottie JSON animations from 34 preset templates with customization options (color/size/frame rate). The description explicitly states '生成' (generate) and 'custom', indicating creation of new animation data.
Documented attack patterns abuse exactly the kind of access qflow_lottie gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Qflow, and nothing reaches the server without passing your rules. This is the rule we recommend for qflow_lottie:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_lottie": {
"limits": [
{
"counter": "qflow_lottie_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}qflow_lottie 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.
Lottie 动画生成：从 34 种预置模板生成自定义 Lottie JSON 动画，支持颜色/尺寸/帧率自定义。. It is categorised as a Write tool in the Qflow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Qflow MCP server in PolicyLayer and add a rule for qflow_lottie: 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 Qflow. Nothing to install.
qflow_lottie 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 qflow_lottie 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 qflow_lottie. 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.
qflow_lottie is provided by the Qflow MCP server (pangu-immortal/qflow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Qflow, 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.
50 Qflow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.