opensensemap.sensors.timeseries

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 52 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/opensensemap.sensors.timeseries.md

WHAT IT DOES

What opensensemap.sensors.timeseries does on Apibase

AI agents call opensensemap.sensors.timeseries to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`limit`	integer	—	Maximum number of measurements to return, newest first (1–10000, default 100).
`box_id`	string	Yes	OpenSenseMap station (box) ID — the 24-character MongoDB ObjectId from box_search or box_detail results (e.g. "578207d56fea661300861f3b").
`to_date`	string	—	End of time range in ISO 8601 format (e.g. "2024-01-02T00:00:00.000Z"). Defaults to now.
`from_date`	string	—	Start of time range in ISO 8601 format (e.g. "2024-01-01T00:00:00.000Z"). Defaults to 2 days ago.
`sensor_id`	string	Yes	Sensor ID within the station — the 24-character MongoDB ObjectId found in sensors_latest or box_detail sensor list (e.g. "578207d56fea661300861f3d").

Parameters from the server's own tool schema.

RISK

Why opensensemap.sensors.timeseries is rated Low

Tool retrieves sensor data without side effects or state changes.

From the tool's definition Retrieve historical time-series measurements. Returns measurement points. No modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs opensensemap.sensors.timeseries safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For opensensemap.sensors.timeseries, this is the rule to start with:

opensensemap.sensors.timeseries Allowed

opensensemap.sensors.timeseries is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "opensensemap.sensors.timeseries": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every opensensemap.sensors.timeseries call is checked against it from then on.

FAQ

Questions about opensensemap.sensors.timeseries

What does the opensensemap.sensors.timeseries tool do? +

Retrieve historical time-series measurements for a specific sensor on an OpenSenseMap station. Returns up to 10,000 measurement points (value + ISO 8601 timestamp) in reverse-chronological order (newest first). Specify box_id and sensor_id (both from box_search or sensors_latest), and optionally narrow the window with from_date/to_date in ISO 8601 format. Sensors on active stations record every 1–10 minutes, so a 24-hour window for a station with 5-min intervals yields ~288 data points. Useful for charting pollution spikes, computing daily averages, building climate datasets, or triggering alerts on threshold crossings. Supports any sensor type: PM2.5 (µg/m³), temperature (°C), relative humidity (%), air pressure (hPa), UV intensity, CO₂ (ppm), and more. Source: OpenSenseMap, PDDL 1.0 public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does opensensemap.sensors.timeseries accept? +

opensensemap.sensors.timeseries accepts 5 parameters: limit, box_id, to_date, from_date, sensor_id. Required: box_id, sensor_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on opensensemap.sensors.timeseries? +

Register the Apibase MCP server in PolicyLayer and add a rule for opensensemap.sensors.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 Apibase. Nothing to install.

What risk level is opensensemap.sensors.timeseries? +

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

Can I rate-limit opensensemap.sensors.timeseries? +

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

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

opensensemap.sensors.timeseries is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →