Get command history for an interactive OpenROAD session.
AI agents call get_session_history to retrieve information from Openroad without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical data (command history) from an existing session without executing commands, modifying state, or producing side effects. It is a query operation that falls squarely into the Read category. Severity is low because accessing command history poses minimal risk—it does not execute arbitrary code, delete data, or alter system state.
From the tool's definition Tool name 'get_session_history' and description 'Get command history for an interactive OpenROAD session' indicate a retrieval operation with no modification or execution of commands.
Documented attack patterns abuse exactly the kind of access get_session_history 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 get_session_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_session_history": {}
}
}get_session_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get command history for an interactive OpenROAD session. It is categorised as a Read tool in the Openroad MCP Server, which means it retrieves data without modifying state.
Register the Openroad MCP server in PolicyLayer and add a rule for get_session_history: 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.
get_session_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_session_history 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 get_session_history. 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.
get_session_history 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.