This record as markdown: /tools/io-github-lokmenower-best-cad-mcp/join-entities.md
What join_entities does on Pypi:best Cad
AI agents use join_entities 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 join_entities is rated Medium
The operation combines existing CAD entities into a single entity—a data modification that creates a new composite structure. This is reversible through undo or manual separation in AutoCAD, making it Write rather than Destructive. Severity is medium because misuse could corrupt drawing geometry or produce unintended merged shapes, but the impact is localized to the drawing and reversible.
From the tool's definition Tool description indicates merging multiple entities of the same type into one continuous entity. In CAD context, this modifies geometry but does not delete the original data irreversibly (entities are merged/combined rather than purged).
Attacks that exploit this kind of access
The rule that runs join_entities 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 join_entities, this is the rule to start with:
join_entities 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 join_entities call is checked against it from then on.
Questions about join_entities
将多个同类型实体合并为一个连续实体。. 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 join_entities: 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.
join_entities 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 join_entities 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 join_entities. 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.
join_entities 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