sch_get_constraint_groups

What sch_get_constraint_groups does on Eda Agent

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

The 'get_' prefix and absence of mutation language (create, delete, update, modify) classify this as a Read operation. The tool retrieves constraint group metadata from a schematic design without side effects. Severity is low because reading design data poses minimal risk even if misused by an agent—it cannot destroy data, execute code, or incur financial consequences.

From the tool's definition Tool name 'sch_get_constraint_groups' indicates a retrieval operation ('get') on schematic design constraints. The empty description is uninformative, but the 'get' verb and context within a design automation server strongly suggest read-only query semantics.

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

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

Questions about sch_get_constraint_groups