Low Risk

inspect_osm_summary

Quick structural summary of an OSM file without loading it into

How to control inspect_osm_summary ↓

What inspect_osm_summary does on Openstudio

AI agents call inspect_osm_summary 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 inspect_osm_summary needs a policy

This tool performs a read-only inspection of an OpenStudio model file to provide a summary view of its structure. It does not modify data, execute simulations, delete anything, or trigger financial operations. The phrase 'without loading it into' suggests a lightweight query operation. This is a classic Read operation—information retrieval with no side effects.

From the tool's definition Tool name 'inspect_osm_summary' and description 'Quick structural summary of an OSM file without loading it into' indicate it retrieves and inspects file metadata/structure without modification or execution.

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

How to control inspect_osm_summary

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

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

inspect_osm_summary 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 inspect_osm_summary

What does the inspect_osm_summary tool do? +

Quick structural summary of an OSM file without loading it into. 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 inspect_osm_summary? +

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

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

Can I rate-limit inspect_osm_summary? +

Yes. Add a rate_limit block to the inspect_osm_summary 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 inspect_osm_summary completely? +

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

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