This record as markdown: /tools/io-github-lokmenower-best-cad-mcp/copy-entity.md
What copy_entity does on Pypi:best Cad
AI agents use copy_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 copy_entity is rated Medium
This tool creates new entities in the CAD drawing by copying existing ones and optionally moving them. This is a reversible write operation—copies can be deleted and positions adjusted. It does not execute arbitrary code, delete irreversibly, move financial value, or merely read data.
From the tool's definition Tool name 'copy_entity' and description '复制实体。可选地在复制后移动新实体' (Copy entity. Optionally move the new entity after copying) indicates creation of new CAD objects through duplication and optional repositioning.
Attacks that exploit this kind of access
The rule that runs copy_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 copy_entity, this is the rule to start with:
copy_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 copy_entity call is checked against it from then on.
Questions about copy_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 copy_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.
copy_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 copy_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 copy_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.
copy_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