Connects to an MQTT broker with the specified parameters.
AI agents invoke mqttConnect to trigger actions in MQTTX SSE Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Establishing a connection to an external MQTT broker is an external operation that creates persistent state (an active network session), analogous to executing a connection command. It is not merely reading data, and while reversible via disconnect, the act of connecting can expose the system to broker-side operations, enable subsequent publish/subscribe actions, and may involve authentication credentials.
From the tool's definition 'Connects to an MQTT broker with the specified parameters' — initiates an external network connection to a broker, triggering an operation whose effects depend on arguments (host, port, credentials, etc.)
Documented attack patterns abuse exactly the kind of access mqttConnect 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 mqttConnect:
{
"version": "1",
"default": "deny",
"tools": {
"mqttConnect": {
"limits": [
{
"counter": "mqttconnect_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}mqttConnect stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Connects to an MQTT broker with the specified parameters. It is categorised as a Execute tool in the MQTTX SSE Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MQTTX SSE Server MCP server in PolicyLayer and add a rule for mqttConnect: 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.
mqttConnect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mqttConnect 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 mqttConnect. 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.
mqttConnect 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.