spine_analyze_json
Read-only Spine JSON inspection tool. Use this to list skeleton metadata, bones, slots, skins, attachments, animations, and inferred common roles such as body, head, tail, eyes, paws, and logo before generating animation keyframes. Do not use it to modify files, call Spine CLI, export, import, or...
This record as markdown: /tools/1425sd-spine-mcp/spine-analyze-json.md
What spine_analyze_json does on Spine
AI agents call spine_analyze_json to retrieve information from Spine without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why spine_analyze_json is rated Low
This is a read-only inspection utility that retrieves and queries data from Spine JSON files. It performs no modifications, deletions, executions, or financial operations. The explicit read-only designation and prohibition against modifications confirm it belongs in the Read category with low severity since it only returns data to the user.
From the tool's definition Tool description states 'Read-only Spine JSON inspection tool' and 'Do not use it to modify files, call Spine CLI, export, import, or automate the Spine UI.' The tool is explicitly designed to 'list skeleton metadata, bones, slots, skins, attachments,…
Attacks that exploit this kind of access
The rule that runs spine_analyze_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_analyze_json, this is the rule to start with:
spine_analyze_json is read-only, so it stays allowed. 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_analyze_json call is checked against it from then on.
Questions about spine_analyze_json
Read-only Spine JSON inspection tool. Use this to list skeleton metadata, bones, slots, skins, attachments, animations, and inferred common roles such as body, head, tail, eyes, paws, and logo before generating animation keyframes. Do not use it to modify files, call Spine CLI, export, import, or automate the Spine UI. It is categorised as a Read tool in the Spine MCP Server, which means it retrieves data without modifying state.
Register the Spine MCP server in PolicyLayer and add a rule for spine_analyze_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_analyze_json is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the spine_analyze_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_analyze_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_analyze_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