mcp_status

MCP server metadata. action: health (SSE/cache metrics), capabilities, prompt_context (AI priming context for this home).

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/mcp-status.md

WHAT IT DOES

What mcp_status does on Openhab

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

This tool only retrieves metadata about the MCP server itself and the home automation system state for AI context. It does not modify data, execute commands, delete anything, or involve financial operations. The 'health' metrics and capabilities inspection are read-only diagnostic operations with minimal blast radius.

From the tool's definition Tool provides 'MCP server metadata' including 'health', 'capabilities', and 'prompt_context' — all informational queries with no side effects or state modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

mcp_status Allowed

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

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

FAQ

Questions about mcp_status

What does the mcp_status tool do? +

MCP server metadata. action: health (SSE/cache metrics), capabilities, prompt_context (AI priming context for this home). 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 mcp_status? +

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

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

Can I rate-limit mcp_status? +

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

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

mcp_status 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_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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