Export the current design to a GDS file.
AI agents use export_design_to_gds to create or update resources in Funky Junction — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Funky Junction environment.
This tool writes data to a file (exports to GDS format), which is a reversible file creation/write operation. It does not delete, execute arbitrary code, move money, or destructively alter existing data. The output is a standard design representation file used in circuit/chip design workflows.
From the tool's definition Tool exports the current quantum circuit design to a GDS (GDES/Geometry Database) file format. GDS export is a standard design output operation that creates or writes a new file containing design data.
Attacks that exploit this kind of access
Export the current design to a GDS file. It is categorised as a Write tool in the Funky Junction MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Funky Junction MCP server in PolicyLayer and add a rule for export_design_to_gds: 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 Funky Junction. Nothing to install.
export_design_to_gds 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_design_to_gds 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_design_to_gds. 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_design_to_gds is provided by the Funky Junction MCP server (paulgoldschmidt/qsim-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 →