openroad_power
Reports power (total/internal/switching/leakage watts plus per-group breakdown) for a placed or routed DEF via OpenSTA report_power. True IR-drop needs PSM, absent in OpenROAD 2.0.
This record as markdown: /tools/zesun33-mcp-openroad/openroad-power.md
What openroad_power does on Mcp Openroad
AI agents call openroad_power to permanently remove resources in Mcp Openroad, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
cwd | string | — | Optional working directory. |
def_file | string | Yes | DEF file path (placed or routed). |
sdc_file | string | — | Optional SDC timing constraints file path. |
timeout_ms | number | — | Timeout in milliseconds. |
top_module | string | Yes | Name of the top-level module. |
clock_period_ns | number | — | Target clock period in ns (default: 1.0). |
Parameters from the server's own tool schema.
Why openroad_power is rated Critical
An AI agent that decides to call openroad_power doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp Openroad is gone. There is no undo for destructive operations.
Risk signalsAccepts file system path (cwd)
Attacks that exploit this kind of access
The rule that runs openroad_power 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_power, this is the rule to start with:
openroad_power is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Openroad, apply this rule, and every openroad_power call is checked against it from then on.
Questions about openroad_power
Reports power (total/internal/switching/leakage watts plus per-group breakdown) for a placed or routed DEF via OpenSTA report_power. True IR-drop needs PSM, absent in OpenROAD 2.0. It is categorised as a Destructive tool in the Mcp Openroad MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
openroad_power accepts 6 parameters: cwd, def_file, sdc_file, timeout_ms, top_module, clock_period_ns. Required: def_file, 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_power: 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_power is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the openroad_power 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_power. 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_power 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.
Across the catalogue