proj_list_variants

A read tool on the Eda Agent MCP server.

SERVEREda Agent SOURCEsalitronic/eda-agent

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eda-agent/proj-list-variants.md

WHAT IT DOES

What proj_list_variants does on Eda Agent

AI agents call proj_list_variants 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.

RISK

Why proj_list_variants is rated Low

The tool appears to retrieve or enumerate variants associated with a project in Altium Designer. The absence of imperative verbs like 'create', 'delete', 'execute', or 'run' in the name, combined with the 'list' pattern consistent with other read operations in the server, indicates this is a safe data retrieval function. No financial, destructive, or code-execution capabilities are implied.

From the tool's definition Tool name 'proj_list_variants' indicates a query operation that lists/enumerates project variants; no description provided, but the 'list' verb and naming convention across the Eda Agent's sibling tools (app_get_active_document, app_get_preferences) suggest…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

proj_list_variants Allowed

proj_list_variants is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Eda Agent, apply this rule, and every proj_list_variants call is checked against it from then on.

FAQ

Questions about proj_list_variants

What does the proj_list_variants tool do? +

proj_list_variants is a read tool on the Eda Agent MCP server. It is categorised as a Read tool in the Eda Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on proj_list_variants? +

Register the Eda Agent MCP server in PolicyLayer and add a rule for proj_list_variants: 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.

What risk level is proj_list_variants? +

proj_list_variants is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit proj_list_variants? +

Yes. Add a rate_limit block to the proj_list_variants 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.

How do I block proj_list_variants completely? +

Set action: deny in the PolicyLayer policy for proj_list_variants. 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.

What MCP server provides proj_list_variants? +

proj_list_variants 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.

KEEP EXPLORING

More on Eda Agent, and thousands of servers like it.

This server

All 345 Eda Agent tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →