Connect to a Plugwise gateway (Adam, Anna, Smile P1, or Stretch) and retrieve gateway information. If no host is provided, automatically connects to the first discovered hub. Returns detailed gateway information including model, type, version, hostname, and MAC address.
AI agents use connect to create or update resources in Plugwise — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Plugwise environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
host | string | — | IP address or hostname of the Plugwise gateway. If omitted, connects to first discovered hub from registry. |
port | number | — | Port number (default: 80) |
password | string | — | Password for the Plugwise gateway (typically the hub name). If omitted and host matches a discovered hub, uses stored password. |
username | string | — | Username (default: smile) |
Parameters from the server's own tool schema.
An AI agent can call connect faster than any human can review — one bad instruction and it creates or modifies resources in Plugwise by the hundred, each call as confident as the last.
Risk signalsAccepts URL/endpoint input (host) · Handles credentials or secrets (password)
Attacks that exploit this kind of access
Connect to a Plugwise gateway (Adam, Anna, Smile P1, or Stretch) and retrieve gateway information. If no host is provided, automatically connects to the first discovered hub. Returns detailed gateway information including model, type, version, hostname, and MAC address. It is categorised as a Write tool in the Plugwise MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
connect accepts 4 parameters: host, port, password, username. The full parameter table on this page comes from the server's own tool schema.
Register the Plugwise MCP server in PolicyLayer and add a rule for connect: 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 Plugwise. Nothing to install.
connect 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 connect 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 connect. 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.
connect is provided by the Plugwise MCP server (plugwise-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 →