mqtt_device_create · MCP API Bridge Server MCP

WHAT IT DOES

What mqtt_device_create does on MCP API Bridge Server

AI agents use mqtt_device_create to create or update resources in MCP API Bridge Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP API Bridge Server environment.

WHY IT NEEDS A POLICY

Why mqtt_device_create needs a policy

This tool creates or initializes a new MQTT device connection, which is a reversible write operation. It modifies the state of the IoT system by adding a new device entity, but the action can be undone by deleting the device. It does not execute arbitrary code, destroy data irreversibly, or move funds, making Write the appropriate category.

From the tool's definition Tool name 'mqtt_device_create' and description '建立 MQTT IoT 裝置連線' (Create MQTT IoT device connection) indicates creation of a new device connection/resource in the MQTT IoT system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mqtt_device_create Rate-limited

mqtt_device_create stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mqtt_device_create": {
      "limits": [
        {
          "counter": "mqtt_device_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP API Bridge Server, so you can run agents against it safely.

FAQ

Questions about mqtt_device_create

What does the mqtt_device_create tool do? +

建立 MQTT IoT 裝置連線. It is categorised as a Write tool in the MCP API Bridge Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mqtt_device_create? +

Register the MCP API Bridge Server MCP server in PolicyLayer and add a rule for mqtt_device_create: 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 MCP API Bridge Server. Nothing to install.

What risk level is mqtt_device_create? +

mqtt_device_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mqtt_device_create? +

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

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

mqtt_device_create is provided by the MCP API Bridge Server MCP server (marty5499/mcp-api-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.