Execute a JavaScript script in the LottieFiles Creator animation editor. The script runs in a sandboxed runtime with access to the `creator` global object (the Creator API) for reading and manipulating animations, layers, shapes, keyframes, colors, and more. Use console.log() to output results — ...
Accepts freeform code/query input (script)
Part of the Creator MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke run_script to trigger processes or run actions in Creator. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
run_script can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
run_script:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Creator policy for all 3 tools.
Agents calling execute-class tools like run_script have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
run_script is one of the high-risk operations in Creator. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Execute a JavaScript script in the LottieFiles Creator animation editor. The script runs in a sandboxed runtime with access to the `creator` global object (the Creator API) for reading and manipulating animations, layers, shapes, keyframes, colors, and more. Use console.log() to output results — all console output is captured and returned. IMPORTANT: Before calling this tool, you MUST call these tools (once per session): 1. get_api_doc — The API type definitions (paginated, read ALL pages). The Creator API is unique and cannot be guessed. 2. get_rules — Conventions like layer ordering that affect visual correctness. Skipping these tools will lead to TypeError and incorrect scripts. Call them first, then write your script.. It is categorised as a Execute tool in the Creator MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for run_script. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Creator MCP server.
run_script 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 run_script rule in your Intercept 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 Intercept policy for run_script. 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.
run_script is provided by the Creator MCP server (@lottiefiles/creator-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.