New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

openroad_floorplan

Initializes ASIC floorplan boundaries, core/die sizing, and I/O pin placement using OpenROAD, generating a floorplan DEF file.

SERVERMcp Openroad SOURCE@zesun33/mcp-openroad
Low RISK CLASS
Category Other
Parameters 82 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-floorplan.md

What openroad_floorplan does on Mcp Openroad

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

ParameterTypeRequiredDescription
cwd string — Optional working directory.
die_width number — Die width in microns (default: 60).
die_height number — Die height in microns (default: 60).
output_def string — Output floorplan DEF file path.
timeout_ms number — Timeout in milliseconds.
top_module string Yes Name of the top-level module.
core_margin number — Margin between die and core in microns (default: 5).
netlist_file string Yes Gate-level Verilog netlist file path.

Parameters from the server's own tool schema.

Why openroad_floorplan is rated Low

Without any rule in front of it, every call an agent makes to openroad_floorplan happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.

Risk signalsAccepts file system path (cwd)

Questions about openroad_floorplan

What does the openroad_floorplan tool do? +

Initializes ASIC floorplan boundaries, core/die sizing, and I/O pin placement using OpenROAD, generating a floorplan DEF file. It is categorised as a Other tool in the Mcp Openroad MCP Server, which means it performs auxiliary operations.

What parameters does openroad_floorplan accept? +

openroad_floorplan accepts 8 parameters: cwd, die_width, die_height, output_def, timeout_ms, top_module, core_margin, netlist_file. Required: top_module, netlist_file. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on openroad_floorplan? +

Register the Mcp Openroad MCP server in PolicyLayer and add a rule for openroad_floorplan: 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_floorplan? +

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

Can I rate-limit openroad_floorplan? +

Yes. Add a rate_limit block to the openroad_floorplan 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_floorplan completely? +

Set action: deny in the PolicyLayer policy for openroad_floorplan. 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_floorplan? +

openroad_floorplan 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Openroad's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.