Disconnects from the currently connected MQTT broker.
AI agents call mqttDisconnect as a supporting operation in MQTTX SSE Server workflows.
Disconnecting from an MQTT broker is a network session teardown, not a data deletion, code execution, financial operation, or data write. It terminates the connection but does not irreversibly destroy data or overwrite anything. The closest category would be 'Other' since it's a connectivity/session management action. Misuse could disrupt message flow but has limited blast radius as reconnection is straightforward.
From the tool's definition Disconnects from the currently connected MQTT broker
Documented attack patterns abuse exactly the kind of access mqttDisconnect gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MQTTX SSE Server, and nothing reaches the server without passing your rules. This is the rule we recommend for mqttDisconnect:
{
"version": "1",
"default": "deny",
"tools": {
"mqttDisconnect": {
"limits": [
{
"counter": "mqttdisconnect_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}mqttDisconnect gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Disconnects from the currently connected MQTT broker. It is categorised as a Other tool in the MQTTX SSE Server MCP Server, which means it performs auxiliary operations.
Register the MQTTX SSE Server MCP server in PolicyLayer and add a rule for mqttDisconnect: 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 MQTTX SSE Server. Nothing to install.
mqttDisconnect is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mqttDisconnect 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 mqttDisconnect. 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.
mqttDisconnect is provided by the MQTTX SSE Server MCP server (ysfscream/mqttx-mcp-sse-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MQTTX SSE Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 MQTTX SSE Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.