list_hubs

List all registered Plugwise hubs from the /hubs folder and in-memory registry. Returns hub information including name, IP address, model, and firmware version for each discovered hub.

Server Plugwise MCP Server tommertom/plugwise-mcp
Category Read
Risk class Low
Parameters 00 required

What list_hubs does on Plugwise MCP Server

AI agents call list_hubs to retrieve information from Plugwise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_hubs needs a policy

This tool queries and returns hub metadata (name, IP address, model, firmware version) from a registry or file system without making any changes to the system state, executing code, or affecting device operations. It is a straightforward informational read operation with minimal security risk.

From the tool's definition Tool name 'list_hubs' and description 'List all registered Plugwise hubs...Returns hub information' indicate data retrieval with no modification, deletion, or execution of commands.

Questions about list_hubs

What does the list_hubs tool do? +

List all registered Plugwise hubs from the /hubs folder and in-memory registry. Returns hub information including name, IP address, model, and firmware version for each discovered hub. It is categorised as a Read tool in the Plugwise MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_hubs? +

Register the Plugwise MCP Server MCP server in PolicyLayer and add a rule for list_hubs: 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.

What risk level is list_hubs? +

list_hubs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_hubs? +

Yes. Add a rate_limit block to the list_hubs 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.

How do I block list_hubs completely? +

Set action: deny in the PolicyLayer policy for list_hubs. 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.

What MCP server provides list_hubs? +

list_hubs 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.