get_system_summary

High-density snapshot of the OpenHAB system: items, things, rooms, health.

SERVEROpenhab SOURCEdeswong/openhab-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deswong-openhab-mcp/get-system-summary.md

WHAT IT DOES

What get_system_summary does on Openhab

AI agents call get_system_summary to retrieve information from Openhab without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_system_summary is rated Low

This tool retrieves and queries the current state of the OpenHAB system without creating, modifying, deleting, or executing any operations. It is purely informational, making it a Read operation with low severity since it has no side effects and cannot affect system state or cause harm when misused.

From the tool's definition Description states 'snapshot' of system data (items, things, rooms, health) with no mention of modification, deletion, or execution capabilities. The verb 'get' and noun 'summary' indicate retrieval only.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_system_summary safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Openhab, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_system_summary, this is the rule to start with:

get_system_summary Allowed

get_system_summary is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_system_summary": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Openhab, apply this rule, and every get_system_summary call is checked against it from then on.

FAQ

Questions about get_system_summary

What does the get_system_summary tool do? +

High-density snapshot of the OpenHAB system: items, things, rooms, health. It is categorised as a Read tool in the Openhab MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_system_summary? +

Register the Openhab MCP server in PolicyLayer and add a rule for get_system_summary: 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 Openhab. Nothing to install.

What risk level is get_system_summary? +

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

Can I rate-limit get_system_summary? +

Yes. Add a rate_limit block to the get_system_summary 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 get_system_summary completely? +

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

get_system_summary is provided by the Openhab MCP server (deswong/openhab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Openhab, and thousands of servers like it.

This server

All 25 Openhab tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →