This record as markdown: /tools/io-github-lokmenower-best-cad-mcp/move-entity.md
What move_entity does on Pypi:best Cad
AI agents use move_entity to create or update resources in Pypi:best Cad, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pypi:best Cad environment.
Why move_entity is rated Medium
This tool creates reversible modifications to CAD drawing data by relocating entities. It is not destructive (entities are not deleted), not execute (no arbitrary code execution), and not financial. The blast radius is medium because unintended entity movements could corrupt drawing layouts, require manual correction, but remain undoable through standard CAD undo operations.
From the tool's definition Tool name 'move_entity' combined with server context (Windows AutoCAD MCP for CAD automation) indicates modification of drawing objects.
Attacks that exploit this kind of access
The rule that runs move_entity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pypi:best Cad, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_entity, this is the rule to start with:
move_entity 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 Pypi:best Cad, apply this rule, and every move_entity call is checked against it from then on.
Questions about move_entity
移动实体到新位置。. It is categorised as a Write tool in the Pypi:best Cad MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pypi:best Cad MCP server in PolicyLayer and add a rule for move_entity: 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 Pypi:best Cad. Nothing to install.
move_entity 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_entity 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_entity. 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_entity is provided by the Pypi:best Cad MCP server (pypi:best-cad-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pypi:best Cad, and thousands of servers like it.
This server
Across the catalogue