Move an object to a new position
AI agents use move_object to create or update resources in Threlte — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Threlte environment.
Moving an object changes its position/state in the scene but is reversible (the object can be moved back). This is a Write operation — it modifies scene data without deleting anything or executing arbitrary code.
From the tool's definition Move an object to a new position
Documented attack patterns abuse exactly the kind of access move_object gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Threlte, and nothing reaches the server without passing your rules. This is the rule we recommend for move_object:
{
"version": "1",
"default": "deny",
"tools": {
"move_object": {
"limits": [
{
"counter": "move_object_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_object 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.
Free to start. No card required.
Move an object to a new position. It is categorised as a Write tool in the Threlte MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Threlte MCP server in PolicyLayer and add a rule for move_object: 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 Threlte. Nothing to install.
move_object 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 move_object 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 move_object. 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.
move_object is provided by the Threlte MCP server (serifeusstudio/threlte-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Threlte, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 Threlte tools catalogued and risk-classified — across an index of 43,000+ MCP servers.