openroad_sta_corners

Runs static timing analysis across multiple Liberty corners (one .lib per corner) on a DEF file, reporting per-corner WNS/TNS plus the worst corner.

SERVERMcp Openroad SOURCE@zesun33/mcp-openroad

Low RISK CLASS

Category Other

Parameters 83 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/zesun33-mcp-openroad/openroad-sta-corners.md

WHAT IT DOES

What openroad_sta_corners does on Mcp Openroad

AI agents call openroad_sta_corners as a supporting operation in Mcp Openroad workflows.

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 per corner in milliseconds.
`top_module`	string	Yes	Name of the top-level module.
`corner_names`	array	—	Optional corner labels matching liberty_files order.
`liberty_files`	array	Yes	Liberty (.lib) files, one per corner.
`clock_period_ns`	number	—	Target clock period in ns (default: 1.0).

Parameters from the server's own tool schema.

RISK

Why openroad_sta_corners is rated Low

Without any rule in front of it, every call an agent makes to openroad_sta_corners 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

RECOMMENDED RULE

The rule that runs openroad_sta_corners 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_sta_corners, this is the rule to start with:

openroad_sta_corners Rate-limited

openroad_sta_corners gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "openroad_sta_corners": {
      "limits": [
        {
          "counter": "openroad_sta_corners_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Openroad, apply this rule, and every openroad_sta_corners call is checked against it from then on.

FAQ

Questions about openroad_sta_corners

What does the openroad_sta_corners tool do? +

Runs static timing analysis across multiple Liberty corners (one .lib per corner) on a DEF file, reporting per-corner WNS/TNS plus the worst corner. It is categorised as a Other tool in the Mcp Openroad MCP Server, which means it performs auxiliary operations.

What parameters does openroad_sta_corners accept? +

openroad_sta_corners accepts 8 parameters: cwd, def_file, sdc_file, timeout_ms, top_module, corner_names, liberty_files, clock_period_ns. Required: def_file, top_module, liberty_files. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on openroad_sta_corners? +

Register the Mcp Openroad MCP server in PolicyLayer and add a rule for openroad_sta_corners: 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.

What risk level is openroad_sta_corners? +

openroad_sta_corners is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit openroad_sta_corners? +

Yes. Add a rate_limit block to the openroad_sta_corners 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.

How do I block openroad_sta_corners completely? +

Set action: deny in the PolicyLayer policy for openroad_sta_corners. 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.

What MCP server provides openroad_sta_corners? +

openroad_sta_corners 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.

KEEP EXPLORING

More on Mcp Openroad, and thousands of servers like it.

This server

All 12 Mcp Openroad tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →