This record as markdown: /tools/io-github-lokmenower-best-cad-mcp/select-by-fence.md
What select_by_fence does on Pypi:best Cad
AI agents use select_by_fence 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 select_by_fence is rated Medium
While the tool appears to be a selection operation (which might seem read-only), selections in AutoCAD represent a modification of the drawing's state—specifically the active selection set. This is reversible (selections can be cleared or changed), making it a Write operation rather than pure Read. It does not execute arbitrary code, delete data, or move money, so Write is the appropriate category.
From the tool's definition Tool name 'select_by_fence' combined with description indicating selection of entities that intersect with a specified polyline. In AutoCAD context, this modifies the active selection set, which is a stateful property of the drawing session.
Attacks that exploit this kind of access
The rule that runs select_by_fence 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 select_by_fence, this is the rule to start with:
select_by_fence 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 select_by_fence call is checked against it from then on.
Questions about select_by_fence
栏选:选择与指定折线相交的所有实体。. 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 select_by_fence: 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.
select_by_fence 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 select_by_fence 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 select_by_fence. 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.
select_by_fence 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