createState
A write tool on the Spline MCP server.
This record as markdown: /tools/aydinfer-spline-mcp-server/createstate.md
What createState does on Spline MCP Server
AI agents use createState to create or update resources in Spline MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spline MCP Server environment.
Why createState is rated Medium
State creation in a 3D design tool is a reversible modification operation—new states can be deleted or modified without destroying the underlying scene. This is Write-level risk, not Execute, because it creates data structures rather than running arbitrary code. Severity is medium because misuse could create unwanted states, but effects are reversible and limited to the design project scope.
From the tool's definition Tool name is 'createState' with empty description; sibling tools show this is a Spline 3D design tool context where 'add' and 'apply' operations modify design state.
Attacks that exploit this kind of access
The rule that runs createState safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Spline MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For createState, this is the rule to start with:
createState 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Spline MCP Server, apply this rule, and every createState call is checked against it from then on.
Questions about createState
createState is a write tool on the Spline MCP Server MCP server. It is categorised as a Write tool in the Spline MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Spline MCP Server MCP server in PolicyLayer and add a rule for createState: 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 Spline MCP Server. Nothing to install.
createState is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the createState 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 createState. 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.
createState is provided by the Spline MCP Server MCP server (aydinfer/spline-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Spline MCP Server, and thousands of servers like it.
This server
Across the catalogue