query_rules

Read automation rules. action: all (list all), get (by UID).

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/query-rules.md

WHAT IT DOES

What query_rules does on Openhab

AI agents call query_rules 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 query_rules is rated Low

This tool queries and lists automation rules without executing them, modifying them, or triggering any side effects. It is a read-only operation that retrieves rule metadata and configuration. The low severity reflects minimal risk even if misused by an AI agent, as viewing rule definitions poses no direct harm to the home automation system.

From the tool's definition Tool description explicitly states 'Read automation rules' with actions 'all (list all), get (by UID)' — pure retrieval with no modification or execution of rules.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs query_rules 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 query_rules, this is the rule to start with:

query_rules Allowed

query_rules 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": {
    "query_rules": {}
  }
}

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 query_rules call is checked against it from then on.

FAQ

Questions about query_rules

What does the query_rules tool do? +

Read automation rules. action: all (list all), get (by UID). 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 query_rules? +

Register the Openhab MCP server in PolicyLayer and add a rule for query_rules: 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 query_rules? +

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

Can I rate-limit query_rules? +

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

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

query_rules 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

claude_query on Claude Bridge → The MCP Attack Database →

Guides

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