Low Risk

extract_summary_metrics

extract_summary_metrics

How to control extract_summary_metrics ↓

What extract_summary_metrics does on Openstudio

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

The tool appears designed to retrieve or aggregate summary metrics from building energy simulation models or results. No description provided, lowering confidence slightly, but the naming pattern and server purpose (querying and analyzing results) strongly indicate a Read operation with no side effects. Blast radius if misused is minimal—worst case an agent extracts irrelevant or unnecessary data.

From the tool's definition Tool name 'extract_summary_metrics' combined with server context indicating OpenStudio energy simulation analysis. The verb 'extract' and noun 'metrics' suggest data retrieval.

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

How to control extract_summary_metrics

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

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

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

What does the extract_summary_metrics tool do? +

extract_summary_metrics. 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 extract_summary_metrics? +

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

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

Can I rate-limit extract_summary_metrics? +

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

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

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