openroad_detail_route
Runs detailed routing on a globally-routed DEF file and reports DRC issue counts with samples. Completes even with findings; check drcIssues before signoff.
This record as markdown: /tools/zesun33-mcp-openroad/openroad-detail-route.md
What openroad_detail_route does on Mcp Openroad
AI agents call openroad_detail_route as a supporting operation in Mcp Openroad workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
cwd | string | — | Optional working directory. |
output_def | string | — | Output detail-routed DEF file path. |
routed_def | string | Yes | Globally-routed DEF file path (output of openroad_route). |
timeout_ms | number | — | Timeout in milliseconds. |
top_module | string | Yes | Name of the top-level module. |
Parameters from the server's own tool schema.
Why openroad_detail_route is rated Low
Without any rule in front of it, every call an agent makes to openroad_detail_route 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_detail_route 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_detail_route, this is the rule to start with:
openroad_detail_route 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_detail_route call is checked against it from then on.
Questions about openroad_detail_route
Runs detailed routing on a globally-routed DEF file and reports DRC issue counts with samples. Completes even with findings; check drcIssues before signoff. It is categorised as a Other tool in the Mcp Openroad MCP Server, which means it performs auxiliary operations.
openroad_detail_route accepts 5 parameters: cwd, output_def, routed_def, timeout_ms, top_module. Required: routed_def, top_module. 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_detail_route: 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_detail_route 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_detail_route 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_detail_route. 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_detail_route 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