spine.changeSkeleton

SERVERPixi Inspector SOURCEpixi-inspector-mcp

Low RISK CLASS

Category Other

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/pixi-inspector-mcp/spine.changeskeleton.md

WHAT IT DOES

What spine.changeSkeleton does on Pixi Inspector

AI agents call spine.changeSkeleton as a supporting operation in Pixi Inspector workflows.

Parameter	Type	Required	Description
`id`	string	Yes	Spine node id from spine.list
`tabId`	integer	—	Legacy: a bare tab id, resolved inside the browser this session is already working with. Prefer `target`, which is unambiguous across browsers.
`target`	string	—	Drive a specific tab: a target id like "b7a3c1#487" from status/use_target/CHOOSE_TARGET. Omit to use this session's chosen tab (or the only available one). Pas
`frameId`	integer	—	Escape hatch: drive a specific FRAME of the tab (0 is the top frame). Normally unnecessary — the extension picks the frame running the game (canvas owner first,
`skeletonId`	string	Yes	Target skeleton id/name

Parameters from the server's own tool schema.

RISK

Why spine.changeSkeleton is rated Low

Without any rule in front of it, every call an agent makes to spine.changeSkeleton happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs spine.changeSkeleton safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pixi Inspector, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spine.changeSkeleton, this is the rule to start with:

spine.changeSkeleton Rate-limited

spine.changeSkeleton gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "spine.changeSkeleton": {
      "limits": [
        {
          "counter": "spine.changeskeleton_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about spine.changeSkeleton

What does the spine.changeSkeleton tool do? +

Swaps the Spine's skeleton for another scanned skeleton by id/name. Only skeletons of the same Spine runtime (4.1 / 4.2 / 4.3) as this Spine apply; one of another runtime fails BAD_PARAMS and the Spine is left as it was. It is categorised as a Other tool in the Pixi Inspector MCP Server, which means it performs auxiliary operations.

What parameters does spine.changeSkeleton accept? +

spine.changeSkeleton accepts 5 parameters: id, tabId, target, frameId, skeletonId. Required: id, skeletonId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on spine.changeSkeleton? +

Register the Pixi Inspector MCP server in PolicyLayer and add a rule for spine.changeSkeleton: 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 Pixi Inspector. Nothing to install.

What risk level is spine.changeSkeleton? +

spine.changeSkeleton is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit spine.changeSkeleton? +

Yes. Add a rate_limit block to the spine.changeSkeleton 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.changeSkeleton completely? +

Set action: deny in the PolicyLayer policy for spine.changeSkeleton. 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.changeSkeleton? +

spine.changeSkeleton is provided by the Pixi Inspector MCP server (pixi-inspector-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pixi Inspector, and thousands of servers like it.

This server

All 63 Pixi Inspector tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →