audit_find_inconsistent_track_widths

What audit_find_inconsistent_track_widths does on Altium-MCP-Suite

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

Why audit_find_inconsistent_track_widths is rated Low

Despite the empty description reducing confidence slightly, the semantics of 'audit_find_*' pattern across PCB/schematic design tools typically denotes read-only inspection of design attributes (in this case, track widths). There is no indication of data modification, deletion, or external execution. The context of Altium Designer auditing (design review, validation) supports classification as a Read operation.

From the tool's definition Tool name contains 'find' and 'audit', suggesting data retrieval and review operations. The 'audit_' prefix indicates inspection/analysis of design properties rather than modification.

The rule that runs audit_find_inconsistent_track_widths safely

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

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

Questions about audit_find_inconsistent_track_widths