Low Risk

get_versions

OpenStudio SDK, EnergyPlus, and Ruby interpreter versions in the container.

How to control get_versions ↓

What get_versions does on Openstudio

AI agents call get_versions 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.

Low Risk

Why get_versions needs a policy

This tool only retrieves and returns version information about installed software components. It performs no writes, deletions, code execution, or financial operations. The data returned is static system metadata with minimal sensitivity. Confidence is high because the function name and description clearly indicate a simple informational read operation.

From the tool's definition Tool name is 'get_versions' and description states it retrieves 'OpenStudio SDK, EnergyPlus, and Ruby interpreter versions in the container' — a pure query operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_versions gives an agent:

How to control get_versions

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 get_versions:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_versions": {}
  }
}

get_versions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Openstudio — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_versions

What does the get_versions tool do? +

OpenStudio SDK, EnergyPlus, and Ruby interpreter versions in the container. It is categorised as a Read tool in the Openstudio MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_versions? +

Register the Openstudio MCP server in PolicyLayer and add a rule for get_versions: 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.

What risk level is get_versions? +

get_versions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_versions? +

Yes. Add a rate_limit block to the get_versions 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.

How do I block get_versions completely? +

Set action: deny in the PolicyLayer policy for get_versions. 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.

What MCP server provides get_versions? +

get_versions 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.

Enforce policy on every Openstudio tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.