AI agents use export_symbol_svg to create or update resources in Kicad — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kicad environment.
The tool generates and exports symbol data to SVG format, which is a file creation/write operation. While the blast radius is moderate (could fill disk space or overwrite existing SVG files if not handled carefully), it's reversible and doesn't constitute destructive deletion. Confidence is reduced slightly due to lack of detail about overwrite behavior or file handling specifics in the description.
From the tool's definition Tool performs 'Export symbol library to SVG images' – a write operation that creates/generates output files. Not destructive (doesn't delete or overwrite existing data irreversibly), not execute (doesn't run arbitrary code), not financial/read.
Attacks that exploit this kind of access
Export symbol library to SVG images. It is categorised as a Write tool in the Kicad MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kicad MCP server in PolicyLayer and add a rule for export_symbol_svg: 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 Kicad. Nothing to install.
export_symbol_svg 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 export_symbol_svg 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 export_symbol_svg. 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.
export_symbol_svg is provided by the Kicad MCP server (productofamerica/mcp-server-kicad). 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 →