Get detailed information about a specific space.
AI agents call get_space_details 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 performs a read-only query operation on OpenStudio building energy model data. It retrieves and returns information about a space without altering model state, executing code, or triggering external side effects. The verb 'get' and passive retrieval nature clearly indicate a Read category with low severity—misuse would only expose data, not compromise model integrity or external systems.
From the tool's definition Tool name is 'get_space_details' and description states it retrieves 'detailed information about a specific space' with no mention of modification, deletion, or external execution.
Documented attack patterns abuse exactly the kind of access get_space_details 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_space_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_space_details": {}
}
}get_space_details 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 detailed information about a specific space. 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_space_details: 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_space_details 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_space_details 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_space_details. 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_space_details 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.