AI agents use kicad.create_board_outline to create or update resources in Eda — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Eda environment.
Creating a board outline is a reversible design modification that establishes the physical boundary of a PCB layout. This is Write-category because it creates/modifies design data without permanent deletion and is not executing arbitrary code or commands. Severity is medium because incorrect outlines could impact manufacturing, but the operation itself is undoable/editable in KiCad.
From the tool's definition Tool name 'create_board_outline' indicates creation of PCB board boundary geometry; sibling tools (add_component, add_wire, add_line) are all Write operations that create design elements. Description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
kicad.create_board_outline. It is categorised as a Write tool in the Eda MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Eda MCP server in PolicyLayer and add a rule for kicad.create_board_outline: 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.create_board_outline 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 kicad.create_board_outline 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.create_board_outline. 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.create_board_outline 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 →