updateCloner
A write tool on the Spline MCP server.
This record as markdown: /tools/aydinfer-spline-mcp-server/updatecloner.md
What updateCloner does on Spline MCP Server
AI agents use updateCloner 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 updateCloner is rated Medium
The tool appears to modify an existing cloner object in Spline's 3D design system. This is a Write operation because it changes object state reversibly without destructive consequences. Severity is medium because misuse could corrupt a design project's structure, but effects are limited to the current design context and reversible through undo operations typical in design software.
From the tool's definition Tool name 'updateCloner' indicates modification of a cloner object. Sibling tools show this server manipulates 3D design elements (addCamera, addDirectionalLight, addMaterialLayer, addPhysicsBody, etc.), and the server description mentions 'creating…
Attacks that exploit this kind of access
The rule that runs updateCloner 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 updateCloner, this is the rule to start with:
updateCloner 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 updateCloner call is checked against it from then on.
Questions about updateCloner
updateCloner 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 updateCloner: 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.
updateCloner 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 updateCloner 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 updateCloner. 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.
updateCloner 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