spine_open_project
Use 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, or waiting for editor operations to finish.
This record as markdown: /tools/1425sd-spine-mcp/spine-open-project.md
What spine_open_project does on Spine
AI agents invoke spine_open_project 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_open_project is rated High
This tool launches an external GUI application (the Spine editor) to open a project file. This constitutes triggering an external operation, placing it in the Execute category. It is not merely reading data, nor does it modify or delete data directly.
From the tool's definition 'open a .spine project in the local Spine application' — triggers an external application launch/operation on the local system
Attacks that exploit this kind of access
The rule that runs spine_open_project 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_open_project, this is the rule to start with:
spine_open_project 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_open_project call is checked against it from then on.
Questions about spine_open_project
Use 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, or waiting for editor operations to finish. 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_open_project: 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_open_project 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_open_project 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_open_project. 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_open_project 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