easyeda_clear_schematic_selection
Deselect everything on the current schematic.
This record as markdown: /tools/eda-agent/easyeda-clear-schematic-selection.md
What easyeda_clear_schematic_selection does on Eda Agent
AI agents call easyeda_clear_schematic_selection to permanently remove resources in Eda Agent, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why easyeda_clear_schematic_selection is rated Critical
An AI agent that decides to call easyeda_clear_schematic_selection doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Eda Agent is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs easyeda_clear_schematic_selection 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 easyeda_clear_schematic_selection, this is the rule to start with:
easyeda_clear_schematic_selection is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Eda Agent, apply this rule, and every easyeda_clear_schematic_selection call is checked against it from then on.
Questions about easyeda_clear_schematic_selection
Deselect everything on the current schematic. It is categorised as a Destructive tool in the Eda Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Eda Agent MCP server in PolicyLayer and add a rule for easyeda_clear_schematic_selection: 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 Eda Agent. Nothing to install.
easyeda_clear_schematic_selection is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the easyeda_clear_schematic_selection 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.
Set action: deny in the PolicyLayer policy for easyeda_clear_schematic_selection. 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.
easyeda_clear_schematic_selection is provided by the Eda Agent MCP server (salitronic/eda-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Eda Agent, and thousands of servers like it.
Across the catalogue