opensensemap.boxes.detail
Get full metadata and sensor list for a specific OpenSenseMap sensor station by its box ID. Returns station name, coordinates, exposure type, hardware model, creation date, and a complete list of all sensors with their IDs, titles, units, sensor types, and latest measurement values. Use this to d...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/opensensemap.boxes.detail.md
What opensensemap.boxes.detail does on Apibase
AI agents call opensensemap.boxes.detail 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 |
|---|---|---|---|
box_id | string | Yes | OpenSenseMap station (box) ID — the 24-character MongoDB ObjectId from box_search results (e.g. "578207d56fea661300861f3b"). |
Parameters from the server's own tool schema.
Why opensensemap.boxes.detail is rated Low
Retrieves publicly available sensor station metadata and configuration without side effects.
From the tool's definition Get full metadata and sensor list for a specific OpenSenseMap sensor station by its box ID.
Attacks that exploit this kind of access
The rule that runs opensensemap.boxes.detail 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.boxes.detail, this is the rule to start with:
opensensemap.boxes.detail is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every opensensemap.boxes.detail call is checked against it from then on.
Questions about opensensemap.boxes.detail
Get full metadata and sensor list for a specific OpenSenseMap sensor station by its box ID. Returns station name, coordinates, exposure type, hardware model, creation date, and a complete list of all sensors with their IDs, titles, units, sensor types, and latest measurement values. Use this to discover the sensor IDs needed for sensor_timeseries calls. A station typically has 3–12 sensors covering combinations of: temperature (°C), relative humidity (%), air pressure (hPa), PM2.5 (µg/m³), PM10 (µg/m³), UV intensity (µW/cm²), illuminance (lx), CO₂ (ppm), and more. Obtain the box_id from box_search results. 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.
opensensemap.boxes.detail accepts 1 parameter: box_id. Required: box_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for opensensemap.boxes.detail: 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.
opensensemap.boxes.detail 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 opensensemap.boxes.detail 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 opensensemap.boxes.detail. 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.
opensensemap.boxes.detail 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.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue