spine_clean
Use 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 textures, or automate the editor UI.
This record as markdown: /tools/1425sd-spine-mcp/spine-clean.md
What spine_clean does on Spine
AI agents invoke spine_clean to trigger actions in Spine. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why spine_clean is rated High
The tool runs a CLI command (Spine CLI with -m flag) which constitutes executing an external process. The description explicitly says 'Do not use it to delete files' suggesting it doesn't irreversibly destroy data, but running CLI cleanup operations can modify project state. This puts it in the Execute category as it triggers an external CLI operation whose effects depend on the input project.
From the tool's definition 'run Spine CLI animation clean up with -m on a project' — executes the Spine CLI with a flag against a project file
Attacks that exploit this kind of access
The rule that runs spine_clean 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_clean, this is the rule to start with:
spine_clean stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_clean call is checked against it from then on.
Questions about spine_clean
Use 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 textures, or automate the editor UI. It is categorised as a Execute tool in the Spine MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Spine MCP server in PolicyLayer and add a rule for spine_clean: 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_clean is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the spine_clean 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_clean. 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_clean 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