Create a new interactive OpenROAD session.
AI agents invoke create_interactive_session to trigger actions in Openroad. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Creating an interactive session spins up a new OpenROAD process/runtime environment. This is an Execute-category action as it initiates an external execution environment whose subsequent effects depend on how it is used. The blast radius is high because an AI agent with an active session can then run arbitrary OpenROAD commands and scripts against chip design data.
From the tool's definition Create a new interactive OpenROAD session
Documented attack patterns abuse exactly the kind of access create_interactive_session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Openroad, and nothing reaches the server without passing your rules. This is the rule we recommend for create_interactive_session:
{
"version": "1",
"default": "deny",
"tools": {
"create_interactive_session": {
"limits": [
{
"counter": "create_interactive_session_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}create_interactive_session stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new interactive OpenROAD session. It is categorised as a Execute tool in the Openroad MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Openroad MCP server in PolicyLayer and add a rule for create_interactive_session: 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 Openroad. Nothing to install.
create_interactive_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_interactive_session 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 create_interactive_session. 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.
create_interactive_session is provided by the Openroad MCP server (the-openroad-project/openroad-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Openroad, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Openroad tools catalogued and risk-classified — across an index of 43,000+ MCP servers.