openroad_pnr
Performs end-to-end automated digital ASIC physical design (floorplanning, placement, routing, and static timing analysis) on a gate-level netlist using OpenROAD, returning area, utilization, wirelength, and timing slack metrics.
This record as markdown: /tools/zesun33-mcp-openroad/openroad-pnr.md
What openroad_pnr does on Mcp Openroad
AI agents call openroad_pnr as a supporting operation in Mcp Openroad workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
cwd | string | — | Optional working directory where source files reside. |
pdn | boolean | — | Insert stdcell PDN after floorplan/tap and before place (Sky130 only; default false). |
sdc_file | string | — | Optional SDC timing constraints file path. |
output_def | string | — | Optional output routed DEF file path. |
timeout_ms | number | — | Timeout in milliseconds (default: 45000). |
top_module | string | Yes | Name of the top-level module to place and route. |
netlist_file | string | Yes | Gate-level Verilog netlist file path. |
clock_period_ns | number | — | Target clock period in ns if no SDC provided (default: 1.0). |
core_utilization | number | — | Target core cell placement density from 0.0 to 1.0 (default: 0.7). |
Parameters from the server's own tool schema.
Why openroad_pnr is rated Low
Without any rule in front of it, every call an agent makes to openroad_pnr happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.
Risk signalsAccepts file system path (cwd)
Attacks that exploit this kind of access
The rule that runs openroad_pnr safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Openroad, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openroad_pnr, this is the rule to start with:
openroad_pnr gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Openroad, apply this rule, and every openroad_pnr call is checked against it from then on.
Questions about openroad_pnr
Performs end-to-end automated digital ASIC physical design (floorplanning, placement, routing, and static timing analysis) on a gate-level netlist using OpenROAD, returning area, utilization, wirelength, and timing slack metrics. It is categorised as a Other tool in the Mcp Openroad MCP Server, which means it performs auxiliary operations.
openroad_pnr accepts 9 parameters: cwd, pdn, sdc_file, output_def, timeout_ms, top_module, netlist_file, clock_period_ns, core_utilization. Required: top_module, netlist_file. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Openroad MCP server in PolicyLayer and add a rule for openroad_pnr: 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 Mcp Openroad. Nothing to install.
openroad_pnr is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the openroad_pnr 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 openroad_pnr. 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.
openroad_pnr is provided by the Mcp Openroad MCP server (@zesun33/mcp-openroad). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Openroad, and thousands of servers like it.
This server
Across the catalogue