spine_generate_animation_json
Generate a modified Spine JSON copy by adding basic animation keyframes to an existing skeleton. Supports breathing, head_float, tail_swing, blink, paw_wave, logo_bounce, and floating by reading bones, slots, skins, and animations from sourceJsonPath. Use this for Photoshop-to-Spine JSON or exist...
This record as markdown: /tools/1425sd-spine-mcp/spine-generate-animation-json.md
What spine_generate_animation_json does on Spine
AI agents use spine_generate_animation_json 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_generate_animation_json is rated Medium
This tool creates and modifies JSON files (animation keyframes and manifest) based on input parameters. While it performs modifications to data structures, these are reversible—the original files remain unchanged and the outputs can be deleted or regenerated. The tool explicitly does not execute Spine binaries, import/export via the GUI, or make irreversible changes to the underlying .spine format.
From the tool's definition Generate a modified Spine JSON copy by adding basic animation keyframes to an existing skeleton. It only writes JSON and generation.manifest.json.
Attacks that exploit this kind of access
The rule that runs spine_generate_animation_json 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_generate_animation_json, this is the rule to start with:
spine_generate_animation_json 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_generate_animation_json call is checked against it from then on.
Questions about spine_generate_animation_json
Generate a modified Spine JSON copy by adding basic animation keyframes to an existing skeleton. Supports breathing, head_float, tail_swing, blink, paw_wave, logo_bounce, and floating by reading bones, slots, skins, and animations from sourceJsonPath. Use this for Photoshop-to-Spine JSON or existing exported Spine JSON. It only writes JSON and generation.manifest.json; it does not open Spine, import, export, pack textures, automate UI, bind mesh, edit weights, or modify .spine binaries. 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_generate_animation_json: 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_generate_animation_json 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_generate_animation_json 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_generate_animation_json. 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_generate_animation_json 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