// SCAN REPORT

CO2 Sensor MCP Server

6 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated: 29 Jun 2026

3 can modify or destroy data

3 read-only

6 tools total

Community server · catalogue entry verified 29/06/2026

How to control CO2 Sensor MCP Server ↓

TOOL MAP

What CO2 Sensor MCP Server exposes to your agents

Read (3) Write / Execute (3) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous CO2 Sensor MCP Server tools

Execute · Medium reconnect_mqtt The tool triggers an external operation — forcing a network reconnection to an MQTT broker. Execute · Medium reconnect_wifi Reconnecting WiFi is an Execute-class action as it triggers an external hardware/network operation. Write · Medium publish_mqtt_data Publishing sensor data to MQTT is a write operation that modifies the state of an external message broker by adding data to a topic.

3 of CO2 Sensor MCP Server's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control CO2 Sensor MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and CO2 Sensor MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "publish_mqtt_data": {
    "limits": [
      {
        "counter": "publish_mqtt_data_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_device_info": {
    "limits": [
      {
        "counter": "get_device_info_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register CO2 Sensor MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON CO2 SENSOR →

Instant setup, no code required.

FULL CATALOGUE

All 6 CO2 Sensor MCP Server tools

EXECUTE 2 tools

Execute reconnect_mqtt Force the device to reconnect to the MQTT broker (NOT IMPLEMENTED) Execute reconnect_wifi Force the device to reconnect to WiFi (NOT IMPLEMENTED)

WRITE 1 tools

Write publish_mqtt_data Publish current sensor data to the MQTT topic (NOT IMPLEMENTED)

READ 3 tools

Read get_device_info Get information about the device Read get_network_status Get WiFi and MQTT connection status (NOT IMPLEMENTED) Read get_sensor_data Get current CO2 ppm readings from the MH-Z19B sensor

FAQ

Questions about CO2 Sensor MCP Server

How do I prevent bulk modifications through CO2 Sensor MCP Server? +

The CO2 Sensor MCP Server server has 1 write tools including publish_mqtt_data. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach CO2 Sensor MCP Server.

How many tools does the CO2 Sensor MCP Server MCP server expose? +

6 tools across 2 categories: Read, Write. 3 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on CO2 Sensor MCP Server? +

Register the CO2 Sensor MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every CO2 Sensor MCP Server tool call.

Deterministic rules across all 6 CO2 Sensor MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CO2 SENSOR →

Instant setup, no code required.

6 CO2 Sensor MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.