AI agents call kicad.list_projects to retrieve information from Eda without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'list_projects' strongly implies a read/query operation that retrieves a list of KiCad projects without side effects. Confidence is reduced due to the empty description.
From the tool's definition Tool name is 'list_projects'; description is empty and uninformative.
Attacks that exploit this kind of access
kicad.list_projects. It is categorised as a Read tool in the Eda MCP Server, which means it retrieves data without modifying state.
Register the Eda MCP server in PolicyLayer and add a rule for kicad.list_projects: 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. Nothing to install.
kicad.list_projects 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 kicad.list_projects 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 kicad.list_projects. 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.
kicad.list_projects is provided by the Eda MCP server (saeronlab/eda-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →