find_entities_by_description

Find scanned entities with rule-based lexical and spatial matching.

SERVERPypi:best Cad SOURCEpypi:best-cad-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about find_entities_by_description

What does the find_entities_by_description tool do? +

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.

How do I enforce a policy on find_entities_by_description? +

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.

What risk level is find_entities_by_description? +

find_entities_by_description is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_entities_by_description? +

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.

How do I block find_entities_by_description completely? +

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.

What MCP server provides find_entities_by_description? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Pypi:best Cad's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.