Low Risk

query_timeseries

query_timeseries

How to control query_timeseries ↓

What query_timeseries does on Openstudio

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

The name strongly suggests this is a read-only operation that retrieves time-series data from simulation results, with no apparent side effects. However, confidence is moderate (0.7) rather than high because the description is empty, preventing verification of actual behavior.

From the tool's definition Tool name 'query_timeseries' indicates data retrieval with no modification capability. Server context (building energy simulation) suggests querying simulation results over time.

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

How to control query_timeseries

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

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

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

What does the query_timeseries tool do? +

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

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

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

Can I rate-limit query_timeseries? +

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

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

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