find_entities_by_description
Find scanned entities with rule-based lexical and spatial matching.
This record as markdown: /tools/io-github-lokmenower-best-cad-mcp/find-entities-by-description.md
What find_entities_by_description does on Pypi:best Cad
AI agents call find_entities_by_description to retrieve information from Pypi:best Cad without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why find_entities_by_description is rated Low
This tool retrieves or queries existing CAD entities based on matching criteria (lexical patterns and spatial relationships). It has no side effects on the drawing data itself — it only locates and returns matching entities. This is characteristic of a Read operation. Severity is low because misuse would at worst return incorrect query results without affecting the drawing or triggering external operations.
From the tool's definition Tool performs 'Find scanned entities' with 'rule-based lexical and spatial matching' — a search/query operation that retrieves data without modifying drawings or executing external commands.
Attacks that exploit this kind of access
The rule that runs find_entities_by_description 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 find_entities_by_description, this is the rule to start with:
find_entities_by_description is read-only, so it stays allowed. 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 find_entities_by_description call is checked against it from then on.
Questions about find_entities_by_description
Find scanned entities with rule-based lexical and spatial matching. It is categorised as a Read tool in the Pypi:best Cad MCP Server, which means it retrieves data without modifying state.
Register the Pypi:best Cad MCP server in PolicyLayer and add a rule for find_entities_by_description: 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.
find_entities_by_description is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the find_entities_by_description 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 find_entities_by_description. 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.
find_entities_by_description 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