AI agents call kicad.help 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.
A 'help' tool almost universally retrieves documentation or usage information, making it a read-only operation with low blast radius. However, the empty description reduces confidence. Given the pattern of sibling tools (all write/modify operations on PCB design files), this tool most likely provides help text or documentation without side effects.
From the tool's definition Tool name is 'kicad.help'; description is empty and uninformative.
Attacks that exploit this kind of access
kicad.help. 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.help: 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.help 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.help 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.help. 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.help 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 →