easyeda_select_layer
Make one layer the active one in the editor.
This record as markdown: /tools/eda-agent/easyeda-select-layer.md
What easyeda_select_layer does on Eda Agent
AI agents invoke easyeda_select_layer to trigger actions in Eda Agent. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why easyeda_select_layer is rated High
Triggers an editor state change by activating a specific layer in the design environment.
From the tool's definition Make one layer the active one in the editor
Attacks that exploit this kind of access
The rule that runs easyeda_select_layer 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_select_layer, this is the rule to start with:
easyeda_select_layer stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Eda Agent, apply this rule, and every easyeda_select_layer call is checked against it from then on.
Questions about easyeda_select_layer
Make one layer the active one in the editor. It is categorised as a Execute tool in the Eda Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Eda Agent MCP server in PolicyLayer and add a rule for easyeda_select_layer: 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_select_layer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the easyeda_select_layer 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_select_layer. 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_select_layer 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