spine.setSkin
Switches the active skin and resets slots to setup pose.
This record as markdown: /tools/pixi-inspector-mcp/spine.setskin.md
What spine.setSkin does on Pixi Inspector
AI agents call spine.setSkin as a supporting operation in Pixi Inspector workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Spine node id from spine.list |
skin | string | Yes | Skin name |
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, |
Parameters from the server's own tool schema.
Why spine.setSkin is rated Low
Without any rule in front of it, every call an agent makes to spine.setSkin happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.
Attacks that exploit this kind of access
The rule that runs spine.setSkin 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.setSkin, this is the rule to start with:
spine.setSkin gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Pixi Inspector, apply this rule, and every spine.setSkin call is checked against it from then on.
Questions about spine.setSkin
Switches the active skin and resets slots to setup pose. It is categorised as a Other tool in the Pixi Inspector MCP Server, which means it performs auxiliary operations.
spine.setSkin accepts 5 parameters: id, skin, tabId, target, frameId. Required: id, skin. The full parameter table on this page comes from the server's own tool schema.
Register the Pixi Inspector MCP server in PolicyLayer and add a rule for spine.setSkin: 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.
spine.setSkin is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the spine.setSkin 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.setSkin. 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.setSkin 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.
More on Pixi Inspector, and thousands of servers like it.
This server
Across the catalogue