list_entities

List all entities currently loaded in the Eyeshot CAD engine.

SERVERTesseract 26 Eyeshot SOURCEa-001-byte/tesseract-26-eyeshot-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/a-001-byte-tesseract-26-eyeshot-mcp/list-entities.md

WHAT IT DOES

What list_entities does on Tesseract 26 Eyeshot

AI agents call list_entities to retrieve information from Tesseract 26 Eyeshot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_entities is rated Low

This tool retrieves and enumerates existing CAD model data from the Eyeshot engine without modifying, executing operations on, or deleting any entities. It is purely informational, making it a Read category tool. Severity is low because even if an AI agent misuses this for reconnaissance, it only exposes model structure information without enabling destructive or operational changes.

From the tool's definition Tool name 'list_entities' combined with description 'List all entities currently loaded in the Eyeshot CAD engine' indicates a query/retrieval operation with no modifications or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_entities safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tesseract 26 Eyeshot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_entities, this is the rule to start with:

list_entities Allowed

list_entities is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_entities": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tesseract 26 Eyeshot, apply this rule, and every list_entities call is checked against it from then on.

FAQ

Questions about list_entities

What does the list_entities tool do? +

List all entities currently loaded in the Eyeshot CAD engine. It is categorised as a Read tool in the Tesseract 26 Eyeshot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_entities? +

Register the Tesseract 26 Eyeshot MCP server in PolicyLayer and add a rule for list_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 Tesseract 26 Eyeshot. Nothing to install.

What risk level is list_entities? +

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

Can I rate-limit list_entities? +

Yes. Add a rate_limit block to the list_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.

How do I block list_entities completely? +

Set action: deny in the PolicyLayer policy for list_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.

What MCP server provides list_entities? +

list_entities is provided by the Tesseract 26 Eyeshot MCP server (a-001-byte/tesseract-26-eyeshot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tesseract 26 Eyeshot, and thousands of servers like it.

This server

All 4 Tesseract 26 Eyeshot tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →