spine_add_simple_animation
Low-level debug tool for adding one simple rotate, translate, or scale bone timeline to a Spine JSON copy. Use this when you already know the exact targetBone and keyframes you want. It only edits JSON and writes generation.manifest.json. Do not use it for natural-language animation planning, pac...
This record as markdown: /tools/1425sd-spine-mcp/spine-add-simple-animation.md
What spine_add_simple_animation does on Spine
AI agents use spine_add_simple_animation 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_add_simple_animation is rated Medium
This tool creates or modifies animation data within JSON files by adding bone timelines (rotate, translate, or scale). While it operates on file copies and is limited to simple transformations (not destructive operations like deletion), it still constitutes data modification.
From the tool's definition The tool description explicitly states it 'edits JSON and writes generation.manifest.json', indicating it modifies data structures. It 'add[s]' animation timelines to a Spine JSON copy, which is a creation/modification operation.
Attacks that exploit this kind of access
The rule that runs spine_add_simple_animation 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_add_simple_animation, this is the rule to start with:
spine_add_simple_animation 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_add_simple_animation call is checked against it from then on.
Questions about spine_add_simple_animation
Low-level debug tool for adding one simple rotate, translate, or scale bone timeline to a Spine JSON copy. Use this when you already know the exact targetBone and keyframes you want. It only edits JSON and writes generation.manifest.json. Do not use it for natural-language animation planning, packing, exporting, UI automation, mesh, IK, weights, or direct .spine binary edits. 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_add_simple_animation: 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_add_simple_animation 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_add_simple_animation 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_add_simple_animation. 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_add_simple_animation 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