proj_set_active_variant
Switch the active project variant.
This record as markdown: /tools/eda-agent/proj-set-active-variant.md
What proj_set_active_variant does on Eda Agent
AI agents use proj_set_active_variant to create or update resources in Eda Agent, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Eda Agent environment.
Why proj_set_active_variant is rated Medium
This tool changes project state by switching which variant is active. This is a reversible modification (you can switch back to a different variant), so it falls under Write rather than Execute or Destructive. The severity is medium because switching variants could affect downstream design operations and exports, but the change is not permanent and does not delete or destroy data.
From the tool's definition "Switch the active project variant" — modifies the active state of a project variant, which changes the design context and may affect subsequent operations on the project.
Attacks that exploit this kind of access
The rule that runs proj_set_active_variant 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 proj_set_active_variant, this is the rule to start with:
proj_set_active_variant stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 proj_set_active_variant call is checked against it from then on.
Questions about proj_set_active_variant
Switch the active project variant. It is categorised as a Write tool in the Eda Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Eda Agent MCP server in PolicyLayer and add a rule for proj_set_active_variant: 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.
proj_set_active_variant is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the proj_set_active_variant 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 proj_set_active_variant. 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.
proj_set_active_variant 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.
This server
Across the catalogue