obj_count

What obj_count does on Eda Agent

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

Why obj_count is rated Low

Based on naming convention, 'obj_count' most likely retrieves a count of objects (schematic elements, PCB components, library items, etc.) without modifying state. The 'count' verb implies data retrieval. However, confidence is moderate because the description is empty and we cannot verify the exact operation. It could theoretically execute code if it triggers backend logic, but the name suggests a simple query.

From the tool's definition Tool name 'obj_count' suggests a counting/enumeration operation, typical of Read operations. Description is empty, limiting definitive classification.

The rule that runs obj_count safely

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

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

Questions about obj_count