AI agents invoke run_qaqc_checks to trigger actions in Openstudio. 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.
This tool triggers automated validation/checking operations (Execute category) rather than passive data retrieval (Read). While the empty description reduces confidence, the naming pattern and context of a simulation tool indicate code execution for analysis.
From the tool's definition Tool name 'run_qaqc_checks' suggests execution of quality assurance/quality control checks. The empty description limits certainty, but in the context of OpenStudio building energy simulation, running QA/QC checks involves executing validation logic and…
Documented attack patterns abuse exactly the kind of access run_qaqc_checks 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 run_qaqc_checks:
{
"version": "1",
"default": "deny",
"tools": {
"run_qaqc_checks": {
"limits": [
{
"counter": "run_qaqc_checks_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_qaqc_checks 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.
run_qaqc_checks. It is categorised as a Execute tool in the Openstudio MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Openstudio MCP server in PolicyLayer and add a rule for run_qaqc_checks: 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.
run_qaqc_checks 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 run_qaqc_checks 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 run_qaqc_checks. 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.
run_qaqc_checks 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.