spine_build_animation_from_existing_project
Build simple animation keyframes on an existing Spine JSON or .spine project. Writes to outputDir, imports into .spine, exports, and can open the result. Requires sourceJsonPath or spineProjectPath. Not for mesh, IK, weights, or UI automation.
This record as markdown: /tools/1425sd-spine-mcp/spine-build-animation-from-existing-project.md
What spine_build_animation_from_existing_project does on Spine
AI agents use spine_build_animation_from_existing_project to create or update resources in Spine, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spine environment.
Why spine_build_animation_from_existing_project is rated Medium
The tool builds animation keyframes and writes output files to a directory, then imports into a .spine project and exports the result. This is a Write operation as it creates/modifies project files in a reversible way (files can be replaced or reverted). It does not delete data irreversibly, execute arbitrary code, or perform financial operations.
From the tool's definition Writes to outputDir, imports into .spine, exports, and can open the result
Attacks that exploit this kind of access
The rule that runs spine_build_animation_from_existing_project safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Spine, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spine_build_animation_from_existing_project, this is the rule to start with:
spine_build_animation_from_existing_project 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Spine, apply this rule, and every spine_build_animation_from_existing_project call is checked against it from then on.
Questions about spine_build_animation_from_existing_project
Build simple animation keyframes on an existing Spine JSON or .spine project. Writes to outputDir, imports into .spine, exports, and can open the result. Requires sourceJsonPath or spineProjectPath. Not for mesh, IK, weights, or UI automation. It is categorised as a Write tool in the Spine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Spine MCP server in PolicyLayer and add a rule for spine_build_animation_from_existing_project: 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 Spine. Nothing to install.
spine_build_animation_from_existing_project 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 spine_build_animation_from_existing_project 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 spine_build_animation_from_existing_project. 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.
spine_build_animation_from_existing_project is provided by the Spine MCP server (1425sd/spine-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Spine, and thousands of servers like it.
This server
Across the catalogue