AI agents call list_custom_measures 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.
The verb 'list' strongly suggests data retrieval without side effects. In the context of an OpenStudio MCP server, this tool likely retrieves metadata about custom measures (simulation customizations). Even in a building energy model context, listing measures does not modify state.
From the tool's definition Tool name 'list_custom_measures' indicates a listing/query operation. The description is empty, so classification relies on the naming convention and context that 'list_*' operations are typically read-only retrieval of data.
Documented attack patterns abuse exactly the kind of access list_custom_measures 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 list_custom_measures:
{
"version": "1",
"default": "deny",
"tools": {
"list_custom_measures": {}
}
}list_custom_measures 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.
list_custom_measures. 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 list_custom_measures: 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.
list_custom_measures 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 list_custom_measures 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 list_custom_measures. 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.
list_custom_measures 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.