Get OpenStudio MCP server information and configuration.
AI agents call get_server_info 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.
This tool retrieves server configuration and information—a read-only operation with no side effects, no data modification, no code execution, and no destructive capabilities. The blast radius of misuse is minimal since exposing server configuration details, while potentially informative to an attacker, does not directly enable unauthorized access or dangerous operations on building models.
From the tool's definition Tool name 'get_server_info' and description 'Get OpenStudio MCP server information and configuration' indicate retrieval of metadata without modification or execution of operations.
Documented attack patterns abuse exactly the kind of access get_server_info 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 get_server_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_server_info": {}
}
}get_server_info 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.
Get OpenStudio MCP server information and configuration. 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 get_server_info: 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.
get_server_info 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 get_server_info 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 get_server_info. 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.
get_server_info 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.