spine_import_json
Use this to import Spine JSON, binary skeleton data, or another supported input into a .spine project via the official Spine CLI. Do not use it for texture packing, project export, editor UI actions, or manual project internals editing.
This record as markdown: /tools/1425sd-spine-mcp/spine-import-json.md
What spine_import_json does on Spine
AI agents use spine_import_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_import_json is rated Medium
This tool creates or modifies project data within .spine files by importing external skeleton/animation data. It is reversible (imported data can be removed or re-imported differently), and does not delete data or execute arbitrary code. While it can affect project structure, the impact is limited to the specific .spine project and the imported data, placing it in the Write category.
From the tool's definition "import Spine JSON, binary skeleton data, or another supported input into a .spine project" — the tool modifies project data by importing and integrating external data into .spine files.
Attacks that exploit this kind of access
The rule that runs spine_import_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_import_json, this is the rule to start with:
spine_import_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_import_json call is checked against it from then on.
Questions about spine_import_json
Use this to import Spine JSON, binary skeleton data, or another supported input into a .spine project via the official Spine CLI. Do not use it for texture packing, project export, editor UI actions, or manual project internals editing. 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_import_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_import_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_import_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_import_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_import_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