IP address or hostname of the Plugwise gateway. If omitted, connects to first discovered hub from registry.
AI agents use connect to create or update resources in Plugwise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Plugwise MCP Server environment.
The tool initiates a network connection to a smart home gateway, which is a stateful write/setup operation rather than a pure read. It modifies the session/connection state. Not destructive, financial, or execute. Confidence is moderate because the description is sparse and primarily describes a parameter rather than the tool's full behavior.
From the tool's definition 'connects to first discovered hub from registry' — establishes a connection to a Plugwise gateway
Attacks that exploit this kind of access
IP address or hostname of the Plugwise gateway. If omitted, connects to first discovered hub from registry. It is categorised as a Write tool in the Plugwise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Plugwise MCP Server 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 MCP Server. 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 MCP server (tommertom/plugwise-mcp). 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 →