get_properties

Get detailed properties for a specific CAD entity by its ID (e.g. type, layer, visibility, colour).

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/get-properties.md

WHAT IT DOES

What get_properties does on Tesseract 26 Eyeshot

AI agents call get_properties 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 get_properties is rated Low

This tool queries and returns metadata about CAD entities (type, layer, visibility, colour) without creating, modifying, deleting, or executing any operations. It is a pure read operation on CAD model data with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name is 'get_properties' and description states it retrieves 'detailed properties for a specific CAD entity' - a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_properties 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 get_properties, this is the rule to start with:

get_properties Allowed

get_properties 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": {
    "get_properties": {}
  }
}

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 get_properties call is checked against it from then on.

FAQ

Questions about get_properties

What does the get_properties tool do? +

Get detailed properties for a specific CAD entity by its ID (e.g. type, layer, visibility, colour). 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 get_properties? +

Register the Tesseract 26 Eyeshot MCP server in PolicyLayer and add a rule for get_properties: 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 get_properties? +

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

Can I rate-limit get_properties? +

Yes. Add a rate_limit block to the get_properties 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 get_properties completely? +

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

get_properties 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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