High-risk tools in Spine
4 of the 16 tools in Spine are classified as high risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at high risk
-
spine_build_animation_from_jsonExecuteOne-step JSON animation pipeline: analyze source JSON, generate animated copy, import to .spine, optionally pack images, export, and open. Use for Spine JSON plus images. Not fo...
-
spine_cleanExecuteUse this to run Spine CLI animation clean up with -m on a project or supported input. Do not use it to delete files, rewrite project internals directly, export assets, pack text...
-
spine_learn_from_corpusExecuteUse this to build the local Spine Corpus Learning Layer. It scans .json and .spine projects, exports .spine files to .cache/corpus-json when needed, extracts naming/animation/st...
-
spine_open_projectExecuteUse this to open a .spine project in the local Spine application so you can continue manual editing. Do not use it for CLI exports, texture packing, JSON import, UI automation, ...
Attacks that target this class
High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.