move_object
Move a CAD entity by a 3D translation vector [x, y, z].
This record as markdown: /tools/a-001-byte-tesseract-26-eyeshot-mcp/move-object.md
What move_object does on Tesseract 26 Eyeshot
AI agents use move_object to create or update resources in Tesseract 26 Eyeshot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tesseract 26 Eyeshot environment.
Why move_object is rated Medium
This tool modifies existing CAD geometry through translation, which qualifies as Write (reversible data modification). Severity is medium because unauthorized movements could corrupt CAD designs or intellectual property, but the operation is non-destructive and can be undone. Confidence is high due to clear description of the modification operation.
From the tool's definition Tool performs 'Move a CAD entity by a 3D translation vector' — modifies object position in CAD model without deletion or creation of new entities. Effect is reversible through counter-movement.
Attacks that exploit this kind of access
The rule that runs move_object safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tesseract 26 Eyeshot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_object, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Tesseract 26 Eyeshot, apply this rule, and every move_object call is checked against it from then on.
Questions about move_object
Move a CAD entity by a 3D translation vector [x, y, z]. It is categorised as a Write tool in the Tesseract 26 Eyeshot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tesseract 26 Eyeshot 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 Tesseract 26 Eyeshot. 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 Tesseract 26 Eyeshot MCP server (a-001-byte/tesseract-26-eyeshot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tesseract 26 Eyeshot, and thousands of servers like it.
This server
Across the catalogue