spine.setAutoUpdate

Enables/disables automatic per-frame updates of the Spine.

SERVERPixi Inspector SOURCEpixi-inspector-mcp

Medium RISK CLASS

Category Write

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.setautoupdate.md

WHAT IT DOES

What spine.setAutoUpdate does on Pixi Inspector

AI agents use spine.setAutoUpdate to create or update resources in Pixi Inspector, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pixi Inspector environment.

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.
`value`	boolean	Yes	Auto-update on/off
`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.

RISK

Why spine.setAutoUpdate is rated Medium

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

Attacks that exploit this kind of access

RECOMMENDED RULE

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

spine.setAutoUpdate Rate-limited

spine.setAutoUpdate 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.setAutoUpdate": {
      "limits": [
        {
          "counter": "spine.setautoupdate_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 Pixi Inspector, apply this rule, and every spine.setAutoUpdate call is checked against it from then on.

FAQ

Questions about spine.setAutoUpdate

What does the spine.setAutoUpdate tool do? +

Enables/disables automatic per-frame updates of the Spine. It is categorised as a Write tool in the Pixi Inspector MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does spine.setAutoUpdate accept? +

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

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

Register the Pixi Inspector MCP server in PolicyLayer and add a rule for spine.setAutoUpdate: 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.setAutoUpdate? +

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

Can I rate-limit spine.setAutoUpdate? +

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

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

spine.setAutoUpdate 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

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