Disconnect from the MQTT broker.
AI agents use mqtt_disconnect to create or update resources in MQTT MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MQTT MCP Server environment.
This tool performs a state modification (disconnecting) but is reversible—a new connection can be established. It does not delete data, execute arbitrary code, create financial obligations, or cause irreversible damage. It falls into Write category as a connection state management operation that modifies system state but can be undone.
From the tool's definition mqtt_disconnect function disconnects from an MQTT broker. The action modifies the connection state by closing an active connection, which is a reversible state change (the connection can be re-established with mqtt_connect).
Attacks that exploit this kind of access
Disconnect from the MQTT broker. It is categorised as a Write tool in the MQTT MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MQTT MCP Server MCP server in PolicyLayer and add a rule for mqtt_disconnect: 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 MQTT MCP Server. Nothing to install.
mqtt_disconnect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mqtt_disconnect 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 mqtt_disconnect. 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.
mqtt_disconnect is provided by the MQTT MCP Server MCP server (sergiudanstan/mqtt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →