proj_list_open
List all currently open projects in the Altium workspace.
This record as markdown: /tools/eda-agent/proj-list-open.md
What proj_list_open does on Eda Agent
AI agents call proj_list_open 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 proj_list_open is rated Low
This tool retrieves information about open projects without modifying, executing, or deleting any data. It is a passive informational query operation typical of the Read category. The blast radius of misuse is minimal since listing projects poses no harm to system integrity or project data.
From the tool's definition Tool name 'proj_list_open' combined with description 'List all currently open projects in the Altium workspace' indicates a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs proj_list_open 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_open, this is the rule to start with:
proj_list_open is read-only, so it stays allowed. 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_list_open call is checked against it from then on.
Questions about proj_list_open
List all currently open projects in the Altium workspace. It is categorised as a Read tool in the Eda Agent MCP Server, which means it retrieves data without modifying state.
Register the Eda Agent MCP server in PolicyLayer and add a rule for proj_list_open: 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_list_open is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the proj_list_open 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_list_open. 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_list_open 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