spine_control_bones
Write custom rotate, translate, and scale timelines for one or more existing bones into a Spine JSON copy. Use this when you know exact bone names and keyframes. This controls bones through JSON animation data only; it does not automate the Spine editor UI, bind meshes, edit weights, create IK, o...
This record as markdown: /tools/1425sd-spine-mcp/spine-control-bones.md
What spine_control_bones does on Spine
AI agents use spine_control_bones 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_control_bones is rated Medium
The tool creates or modifies animation data by writing keyframe timelines into a Spine JSON file. It operates on a copy (not in-place binary mutation), making it reversible. No code execution, deletion, or financial operations are involved.
From the tool's definition Write custom rotate, translate, and scale timelines for one or more existing bones into a Spine JSON copy
Attacks that exploit this kind of access
The rule that runs spine_control_bones 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_control_bones, this is the rule to start with:
spine_control_bones 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_control_bones call is checked against it from then on.
Questions about spine_control_bones
Write custom rotate, translate, and scale timelines for one or more existing bones into a Spine JSON copy. Use this when you know exact bone names and keyframes. This controls bones through JSON animation data only; it does not automate the Spine editor UI, bind meshes, edit weights, create IK, or mutate .spine binaries directly. 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_control_bones: 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_control_bones 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_control_bones 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_control_bones. 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_control_bones 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