Parse simulation errors from eplusout.err into categorized Fatal/Severe/Warning lists.
AI agents call extract_simulation_errors to retrieve information from Openstudio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and categorizes error output from a completed simulation file. It performs data retrieval and analysis only—querying existing simulation results without modifying state, executing code, or performing destructive operations. The verb 'parse' and 'extract' confirm it is a read-only analytical function.
From the tool's definition Tool name 'extract_simulation_errors' and description 'Parse simulation errors from eplusout.err into categorized Fatal/Severe/Warning lists' indicate retrieval and parsing of existing error data with no modification or execution.
Documented attack patterns abuse exactly the kind of access extract_simulation_errors gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Openstudio, and nothing reaches the server without passing your rules. This is the rule we recommend for extract_simulation_errors:
{
"version": "1",
"default": "deny",
"tools": {
"extract_simulation_errors": {}
}
}extract_simulation_errors 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.
Parse simulation errors from eplusout.err into categorized Fatal/Severe/Warning lists. It is categorised as a Read tool in the Openstudio MCP Server, which means it retrieves data without modifying state.
Register the Openstudio MCP server in PolicyLayer and add a rule for extract_simulation_errors: 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 Openstudio. Nothing to install.
extract_simulation_errors 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 extract_simulation_errors 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 extract_simulation_errors. 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.
extract_simulation_errors is provided by the Openstudio MCP server (natlabrockies/openstudio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Openstudio, 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.
146 Openstudio tools catalogued and risk-classified — across an index of 43,000+ MCP servers.