AI agents call list_schedule_rulesets to retrieve information from OpenStudio MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_' prefix strongly indicates a query operation that retrieves and enumerates existing schedule rulesets without modifying model state. This is consistent with other Read-category tools on the server. The lack of description lowers confidence slightly, but the tool name and sibling context support Read classification. No write, execute, destructive, or financial operations are implied.
From the tool's definition Tool name 'list_schedule_rulesets' indicates retrieval/enumeration of schedule ruleset data from OpenStudio models.
Documented attack patterns abuse exactly the kind of access list_schedule_rulesets gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenStudio MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_schedule_rulesets:
{
"version": "1",
"default": "deny",
"tools": {
"list_schedule_rulesets": {}
}
}list_schedule_rulesets 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_schedule_rulesets. It is categorised as a Read tool in the OpenStudio MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenStudio MCP Server MCP server in PolicyLayer and add a rule for list_schedule_rulesets: 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 MCP Server. Nothing to install.
list_schedule_rulesets 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_schedule_rulesets 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_schedule_rulesets. 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_schedule_rulesets is provided by the OpenStudio MCP Server MCP server (roruizf/openstudio-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenStudio MCP Server, 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.
20 OpenStudio MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.