Add a new Plugwise hub by providing its name (used as password). Scans the network to find the hub and stores it in the /hubs folder as a JSON file for future use. The hub name is the unique identifier printed on the back of your Plugwise device.
AI agents use add_hub 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 |
|---|---|---|---|
hubName | string | Yes | The hub name/ID (e.g., glmpuuxg) which is also used as the password. This is the unique identifier found on the back label of your Plugwise hub. |
Parameters from the server's own tool schema.
This tool creates and persists new configuration data (a JSON file storing hub information). This is a Write operation—it modifies the system state by adding a new hub configuration. Severity is medium because misconfiguration could lead to unauthorized hub access or system dysfunction, but the effect is reversible and doesn't directly manipulate critical device settings or cause data loss.
From the tool's definition Tool description states it "stores it in the /hubs folder as a JSON file for future use," indicating creation of new data/configuration files. The action is reversible (can delete the JSON file or re-add with different credentials).
Attacks that exploit this kind of access
Add a new Plugwise hub by providing its name (used as password). Scans the network to find the hub and stores it in the /hubs folder as a JSON file for future use. The hub name is the unique identifier printed on the back of your Plugwise device. 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.
add_hub accepts 1 parameter: hubName. Required: hubName. 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 add_hub: 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.
add_hub 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 add_hub 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 add_hub. 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.
add_hub 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 →