spine_export

SERVERSpine SOURCE1425sd/spine-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1425sd-spine-mcp/spine-export.md

WHAT IT DOES

What spine_export does on Spine

AI agents use spine_export 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.

RISK

Why spine_export is rated Medium

An AI agent can call spine_export faster than any human can review: one bad instruction and it creates or modifies resources in Spine by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs spine_export 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_export, this is the rule to start with:

spine_export Rate-limited

spine_export 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "spine_export": {
      "limits": [
        {
          "counter": "spine_export_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Spine, apply this rule, and every spine_export call is checked against it from then on.

FAQ

Questions about spine_export

What does the spine_export tool do? +

Use this to export a .spine project with the official Spine CLI and an export settings JSON file. Do not use it for texture-only packing, JSON import, editor UI automation, or direct project structure edits. 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.

How do I enforce a policy on spine_export? +

Register the Spine MCP server in PolicyLayer and add a rule for spine_export: 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.

What risk level is spine_export? +

spine_export is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit spine_export? +

Yes. Add a rate_limit block to the spine_export 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.

How do I block spine_export completely? +

Set action: deny in the PolicyLayer policy for spine_export. 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.

What MCP server provides spine_export? +

spine_export 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.

KEEP EXPLORING

More on Spine, and thousands of servers like it.

This server

All 16 Spine tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →